Christopher Blizzard wrote:
> Adam Lock wrote:
>> I've been thinking that the only difference between client and embedding
>> is the list of modules and a few export issues. If we could separate the
>> module lists out into a separate file and sort out the export issues, it
>> would greatly increase the reliability of the embedding builds. The
>> principle reason for failure is that no one remembers to update the
>> embedding build.
>
> That would be good. We should only have to change the arrangement of
> files and sections in the packages-* files. Netscape might have to
> change its build system but that shouldn't be a problem if we give them
> a little warning.
I'm ok with people changing the build system to make embedding easier to
build and maintain as long as we get some warning and it isn't
noticeably slower before.
One thing I would really enjoy seeing is a way to pull and build
embedding, then pull the additional files and build the browser. This
would allow us to deliver the embedding files for testing more quickly
than we do now.
Adding n.p.m.builds to Newsgroups:
-j
