Re: Bug#353381: ITP: freebsd-manpages -- Manual pages for a GNU/kFreeBSD system
David Weinehall wrote: Upstream includes non-free manpages these days, so in reality, we have already forked. Further Debian-specific changes are needed to address bugs such as #295211 (upstream does not document our libc/kernel combination). What manpages in upstream are non-free? Do we have rewritten alternatives in Debian, or are those pages simply removed without replacement? He's talking about manpages-posix and manpages-posix-dev which have been removed from the manpages source package before it is processed into a Debian package. Hence, packaged separately. More info is present in /usr/share/doc/manpages/POSIX-MANPAGES Regards, Joey -- Reading is a lost art nowadays. -- Michael Weber -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#353381: ITP: freebsd-manpages -- Manual pages for a GNU/kFreeBSD system
On Mon, Feb 20, 2006 at 12:42:08PM +0100, Florian Weimer wrote: * David Weinehall: Upstream includes non-free manpages these days, so in reality, we have already forked. Further Debian-specific changes are needed to address bugs such as #295211 (upstream does not document our libc/kernel combination). What manpages in upstream are non-free? Do we have rewritten alternatives in Debian, or are those pages simply removed without replacement? They are simply removed without replacement. For most of the older system calls, the old free manpages (which also contain Linux-specific details) are still included in the upstream package. Only new system calls (such as mq_receive) appear to be undocumented. Do you making a list of the missing pages? I've written quite a few manpages for various programs, and I'm a really frequent user of the already existing manpages, so I can hopefully help contributing a few free replacements. Who knows, if they are good enough we might even be able to convince upstream to replace the non-free versions. Regards: David Weinehall -- /) David Weinehall [EMAIL PROTECTED] /) Rime on my window (\ // ~ // Diamond-white roses of fire // \) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost (/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#353381: ITP: freebsd-manpages -- Manual pages for a GNU/kFreeBSD system
* David Weinehall: Upstream includes non-free manpages these days, so in reality, we have already forked. Further Debian-specific changes are needed to address bugs such as #295211 (upstream does not document our libc/kernel combination). What manpages in upstream are non-free? Do we have rewritten alternatives in Debian, or are those pages simply removed without replacement? They are simply removed without replacement. For most of the older system calls, the old free manpages (which also contain Linux-specific details) are still included in the upstream package. Only new system calls (such as mq_receive) appear to be undocumented. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#353381: ITP: freebsd-manpages -- Manual pages for a GNU/kFreeBSD system
* Russ Allbery: Your points about sync(8) and tzselect(8) seem reasonable on the surface, but the rest of this seems to be disregarding the fact that manpages and manpages-dev are not native packages. Those man pages are included in that package because they're maintained together upstream in a distribution that Debian packages. Upstream includes non-free manpages these days, so in reality, we have already forked. Further Debian-specific changes are needed to address bugs such as #295211 (upstream does not document our libc/kernel combination). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#353381: ITP: freebsd-manpages -- Manual pages for a GNU/kFreeBSD system
On Sun, Feb 19, 2006 at 11:26:57AM +0100, Florian Weimer wrote: * Russ Allbery: Your points about sync(8) and tzselect(8) seem reasonable on the surface, but the rest of this seems to be disregarding the fact that manpages and manpages-dev are not native packages. Those man pages are included in that package because they're maintained together upstream in a distribution that Debian packages. Upstream includes non-free manpages these days, so in reality, we have already forked. Further Debian-specific changes are needed to address bugs such as #295211 (upstream does not document our libc/kernel combination). What manpages in upstream are non-free? Do we have rewritten alternatives in Debian, or are those pages simply removed without replacement? Regards: David Weinehall -- /) David Weinehall [EMAIL PROTECTED] /) Rime on my window (\ // ~ // Diamond-white roses of fire // \) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost (/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#353381: ITP: freebsd-manpages -- Manual pages for a GNU/kFreeBSD system
Sorry to change the topic, but looking at some of the manpages in the manpages package, and some of the pages in the manpages-dev causes me no notice some pages that look like they probably should be in a different package. ld-linux(8) ld-linux.so(8) These probably belong in libc6 which appears to be the provider of ld-linux.so sync(8) This should be deleted. Coreutils (the provider of the sync utility) provides sync(1) for that utility. tzselect(8) This should be removed. it duplicates tzslect(1) (which i presume is provided by the package providing tzselect) ksoftirqd(9) I'm pretty sure this does not belong in the manpage package. As for manpages-dev, it would seem more logical for the linux syscall manpages to be part of linux, and the library documentation to be a part of the libraries that provide the documented functions. If somebody with more time can check on these and, if they are valid, file bugs, I would appreciate it, as I do not have the time right now. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#353381: ITP: freebsd-manpages -- Manual pages for a GNU/kFreeBSD system
Joe Smith [EMAIL PROTECTED] writes: Sorry to change the topic, but looking at some of the manpages in the manpages package, and some of the pages in the manpages-dev causes me no notice some pages that look like they probably should be in a different package. Your points about sync(8) and tzselect(8) seem reasonable on the surface, but the rest of this seems to be disregarding the fact that manpages and manpages-dev are not native packages. Those man pages are included in that package because they're maintained together upstream in a distribution that Debian packages. There are various reasons why the man pages for libc interfaces are in a separate package that probably aren't worth getting into; suffice it to say that libc upstream is probably not going to incorporate and maintain the relevant man pages. Also, it makes less sense than it sounds to include the section two man pages with Linux rather than separately in the manpages-dev package; the userspace API is often not exactly the system call exposed by the kernel, since libc mediates the system call and often does some rejiggering of data types in the process. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
