Mark Hammond wrote:
>  
>  Just to clarify, I believe we are no longer talking about just a *build*
>  system, but instead a *packaging* system, along with some kind of commitment
>  to create binaries using that system?  Specifically, the script of mine and
>  I assume the pyxpcomext project use the standard build process.
>  
>  Even more specifically, to have solved your (Paul's) problem, this system
>  must also be capable of generating binaries for Windows, Mac and Linux, and
>  will presumably need access to that hardware.  Its is probably *not* enough
>  to simply confirm (say) Mac builds work, then assume they will continue to
>  work in the future, and assuming people could simply make their own using
>  that process.  As we saw, that would have fallen over at the first hurdle
>  (the building of it) in the case of Paul.  So I guess I don't see exactly
>  what deliverables you are expecting for this bounty, and how they would have
>  saved your bacon had they been put in place 12 months ago.
>  
>  In general though, I've absolutely no problem with pyxpcomext being the
>  official package.  I was a little dissapointed to have not heard about the
>  effort and that opportunities aren't taken to collaborate on things ("not
>  invented here" syndrome?).  Certainly pyxpcom can only benefit from having a
>  functioning, supported distribution.
>  
>  Cheers,
>  
>  Mark

Hi Mark,

To clarify, although I'm an ActiveState employee, this is *not* an 
ActiveState project. pyxpcomext is something I started in my own time in 
order to solve one problem: "to make PyXPCOM easily available" and 
installable to end users. I only started this about two weeks ago, and 
now I have got something working and worthy of showing to the community 
I announced it here.

I'm not really concerned with the build/packaging scripts and I don't 
want to be labeled as the "official" pyxpcom build, the pyxpcomext 
scripts certainly could do with some additional ideas from your own 
packaging script.

I've put together the pyxpcomext project in order to share the source 
code for how I was making this happen. The build and packaging scripts 
were simply tools that made it easy for *me* to meet my main objective 
of making PyXPCOM available (as there are simply no other PyXPCOM 
packages available).

My aims for the project now are to supply additional builds of PyXPCOM 
for other Mozilla products (Firefox 3, Thunderbird, XulRunner). If 
anyone wants to help that happen I'd very grateful for the assistance 
(especially the Mac OS side). If anyone wants to provide build platforms 
and make official builds with this work, then please go right on 
ahead... I myself do not have the time or the finances for such a 
dedicated activity.

Cheers,
Todd
_______________________________________________
pyxpcom mailing list
pyxpcom@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs