>>>>> "Fabio" == Fabio Massimo Di Nitto <[EMAIL PROTECTED]> writes:
Fabio> Sam Hartman wrote:
>> E
>>
Fabio> [snip]
>>
>>
>> Yet I want to be able to maintain these patches, share them
>> with others and have others be able to add patches.
>>
>> I'd be willing to throw together a build system to do this sort
>> of thing. Would it be useful to anyone besides me? Would it
>> be useful enough for people to give me the current hacked
>> together sources so that I can integrate them into such a
>> system?
>>
>> --Sam
>>
>>
Fabio> If we can make things very
Fabio> clean (but I need help) we can try to place our
Fabio> -netbsd-i386 pkgs directly in the pool.
I think that there may be few packages for wich we can really do this
now. We would need to get changes accepted upstream before we could
do this. I suspect that for some packages we may be able to do that,
but for others, particularly where we are working around stuff that
does not yet build, we will need to maintain local packages, just like
the s390 folks did for a while.
How real do we need to be before ftpmaster will accept uploads?
Fabio> Let me know how you want to procede.
I saw Richard Tibbetts trying to debug apt-get last night. Based on
what he said it seemed like apt-get was failing to parse
/var/lib/dpkg/status; finding a \n where it expected something else.
It segfaulted going off the end of a string at a page boundary. Thus
it's just really good luck we cought the segfault instead of it simply
randomly failing.
The package being parsed was base-files.
So apt-get source seems like a reasonable short-term goal.
What I think I'd like to do is throw together some scripts to take a
well-defined source package either from the pool or an NFS mirror,
unpack, apply BSD-specific patches, then build. I'd also like to have
a script to constitute a new chroot; perhaps doing this by patching
the debootstrap package is the right direction.
Then we could put these scripts along with the patches into a CVS
repository.
