packaging or upgrading bugs. This is my first mentors
upload.
thanks,
--
Ryan Underwood, <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
description users)
> > from asking this again and again.
>
> system-headers-linux is a bit vague and without knowing could be
> associated with the kernel just as strongly as with libc.
>
> How about libc-linux-headers?
I second that, or perhaps libc6-linux-headers.
--
Ryan Underwood, <[EMAIL PROTECTED]>
on would be
maintained in the pool alongside everything else by the buildds. Would
probably require significant reworking of lots of things. :(
Another (rather sillier idea) involved a virtual package *-kernel to
indicate to packages which userland the system was being run on, but I
haven't any idea where I was really going with that.
--
Ryan Underwood, <[EMAIL PROTECTED]>
lization, it seemed like the type of random cruft that
sometimes gets pulled in on dist-upgrade; a name change would help
alleviate that initial perception, IMO. Why not libc6-linux-headers?
--
Ryan Underwood, <[EMAIL PROTECTED]>
greater level
of usability, we can ask these questions again later...
--
Ryan Underwood, , icq=10317253
ded during the package's
postinst or by another script)
--
Ryan Underwood, , icq=10317253
t the replacement
package doesn't silently fail when a directory was attempted to be
overwritten.
--
Ryan Underwood, , icq=10317253
7 matches
Mail list logo
