Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 3 Mar 2008 22:05:36 +0100
From:      "Harald Servat" <redcrash@gmail.com>
To:        "Brooks Davis" <brooks@freebsd.org>
Cc:        freebsd-doc@freebsd.org
Subject:   Re: importing mans from others OSes
Message-ID:  <d825e0270803031305p3f451e4drdfcd5d24b086f915@mail.gmail.com>
In-Reply-To: <20080303200415.GC57043@lor.one-eyed-alien.net>
References:  <d825e0270803031027q1286d04w3c11e757ca9d22d4@mail.gmail.com> <20080303200415.GC57043@lor.one-eyed-alien.net>

next in thread | previous in thread | raw e-mail | index | archive | help
2008/3/3, Brooks Davis <brooks@freebsd.org>:
>
> On Mon, Mar 03, 2008 at 07:27:40PM +0100, Harald Servat wrote:
> > Hello,
> >
> >   I've recently used the call backtrace[1] from the libexec (found in
> > /usr/local/lib) library and I've found it very useful.
> >   As it does not have (nor their relatives) a manual entry, I wondered
> if I
> > could submit one for it. I'm not very skilled on writing manual
> > documentation, and I've never submitted anything to FreeBSD but a port,
> but
> > I'd like to try.
>
>
> libexecinfo is from the port devel/libexecinfo so the base system isn't
> relevant.  If we were to add it to the base the following responses
> would apply.  As it stands, the author could choose to include a GPL or
> APSL licensed manpage, but doing so would not be a step toward getting
> the functionality into the base (perhaps in libutil).
>
>
> >   As I have access to a Linux machine that has this manual entry[2], I
> > wondered if I could use it as a base (or maybe copying it). However, as
> I
> > don't want to start a BSD-License vs GPL-license war, I just want to
> know if
> > it's permitted importing (using as a base, copying, ... or other
> > possibilities that do not come into my mind right now) manual files from
> > other OSes to FreeBSD.
>
>
> There's no chance we'd allow a GPL based manual for a non-GPL based
> function in the system.  We require GPL licensed pieces to be carefully
> isolated and requiring that the documentation for a well integrated
> piece of functionality would make no sense.
>
>
> > Regards and thank you.
> >
> > PS  Googling around, I've also seen that MacOSX has this manual
> entry[3],
> > but it's not as good as [2]. Being MacOSX BSD-based, is the situation
> better
> > to import it?
>
>
> An APSL licensed manpage is basically no better better than a GPL
> licensed one.  If this were in the base we'd require that a manpage be
> licensed under the BSD license .
>
>
> -- Brooks
>
>
Thank you for the explanation.

I'll contact the port maintainer then.

-- 
_________________________________________________________________
Empty your memory,
with a free()...
like a pointer!

If you cast a pointer to an integer,
it becomes an integer,
if you cast a pointer to a struct,
it becomes a struct.

The pointer can crash...,
and can overflow.

Be a pointer my friend...



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d825e0270803031305p3f451e4drdfcd5d24b086f915>