Re: ITP: freebsd-manpages -- Manual pages for a GNU/kFreeBSD system
On Sat, Feb 18, 2006 at 03:30:38AM -0500, Kevin Mark wrote:
> On Sat, Feb 18, 2006 at 09:02:57AM +0100, Javier Fern?ndez-Sanguino Pe?a wrote:
> > On Fri, Feb 17, 2006 at 11:55:22PM +0100, Guerkan Senguen wrote:
> > > Package: wnpp
> > > Severity: wishlist
> > >
> > > * Package name : freebsd-manpages
> > > Version : 6.0
> > Wouldn't this package conflict with the 'manpages' package (which
> > provides them for GNU/Linux) and with the manpages provided by other
> > (core) packages? Or are all manpages going to be renamed so that
> > there is no filename conflict under /usr/share/man/man{2,4}?
> >
> > Regards
> >
> > Javier
>
> Hi,
> if 'manpages' are GFDL and freebsd-manpages is under a bsd license,
> then if freebsd-manpages CAN replace manpages and GFDL docs are
> removed, then there will be no conflict.
a.) The manpages packages does not (AFAIK) contain any GFDL docs;
it's not provided by FSF, since they have a strange aversion
against manpages, and an even stranger predilection for info
pages...
b.) The package itself does not *need* to conflict with the manpages
package, since it provides manpages for 4, 5, and 7,
(and manpages-dev provides 2, and 3).
Replaces: manpages, manpages-dev
is needed though.
HOWEVER, since manpages-dev presumably contains documentations for
interfaces that are Linux specific, it might make sense to have a
Conflicts: manpages, manpages-dev
anyway. This would mean that users of Debian GNU/FreeBSD would lose
the manual-pages for glibc though (since they are also in manpages-dev).
Maybe the manpages source package should be split into more binary
packages? manpages (generic stuff for all Debian systems),
manpages-linux (Linux specific things, like sysfs), manpages-linux-dev
(Linux specific programming interfaces).
Regards: David Weinehall
--
/) David Weinehall <tao@debian.org> /) Rime on my window (\
// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~tao/ (/ Beautiful hoar-frost (/
Reply to: