ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> pyxpcom
pyxpcom
Re: [pyxpcom] What changed in PyXPCOM component registration in 1.9?
by Lauri Kainulainen other posts by this author
Nov 30 2007 1:27AM messages near this date
view in the new Beta List Site
Re: [pyxpcom] What changed in PyXPCOM component registration in 1.9? | Re: [pyxpcom] What changed in PyXPCOM component registration in 1.9?
Mark Hammond wrote:
>  The stuff in the 'component' directory is only supposed to relate to
>  components.  Trying to convince the system to use a more general-purpose
>  directory to store components is not a supported use-case.  Maybe you can
>  step back and tell us what problem you were trying to solve in the first
>  place?

The original problem was that my directory structure that *did* work 
very nicely with the 1.8 branch does not work anymore with trunk. This 
is not a complaint, I was just wondering what changed, since I couldn't 
find any related docs or changelogs.

I guess I'll just add the libs to pythonpath before starting since they 
can't be packaged under the components directory anymore. Or link them 
to /XUL.framework/python/


Cheers,
Lauri

-- 
  Lauri Kainulainen

_______________________________________________
pyxpcom mailing list
pyxpcom@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Thread:
Lauri Kainulainen
Mark Hammond
Lauri Kainulainen
Mark Hammond

Privacy Policy | Email Opt-out | Feedback | Syndication
© 2004 ActiveState, a division of Sophos All rights reserved