9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Balwinder S Dheeman <bsd.SANSPAM@cto.homelinux.net>
To: 9fans@9fans.net
Subject: Re: [9fans] cleaning up gentoo plan9port ebuild
Date: Thu,  4 Mar 2010 17:39:26 +0000	[thread overview]
Message-ID: <tvv467x1fi.ln2@news.homelinux.net> (raw)
In-Reply-To: <twig.1267647720.1847@swcp.com>

On 03/04/2010 01:55 AM, EBo wrote:
> While working on merging and cleaning up the 3 or 4 different portage ebuild
> trees for plan9 and plan9port I ran into a number of things which I need
> clarified:
>
> * Gentoo's plan9port report's the license as MIT, yet the LICENSE file says it
> is Lucent-1.02. Which is correct?
>
> * Gentoo's plan9port also sets DEPEND="x11-apps/xauth".  Is xauth a build or
> runtime dependency?
>
> * Am I correct in my understanding that the only two things that the install
> configuration ("${PLAN9}/INSTALL -c") do is change the hardwired
> /usr/local/plan9 paths, and build the documentation in $PLAN9/dist?
>
> * I've built an updated live ebuild which works directly from the plan9port
> mercurial tree.  Is there enough interest to request that this be added to
> gentoo portage?

I added
http://aur.archlinux.org/packages/plan9us-hg/plan9us-hg/README.too to an
AUR http://aur.archlinux.org/packages.php?ID=32983 for ArchLinux, we
build from mercurial repo.

How about adding a slightly re-phrased REAME.too as follows:

"The bulk of this software is derived from Plan 9 and is thus
distributed under the Lucent Public License, Version 1.02, reproduced
below. There are a few exceptions: libutf, libfmt, and libregexp are
distributed under simpler BSD-like boilerplates.  See the LICENSE files
in those directories.  There are other exceptions, also marked with
LICENSE files in their directories or marked at the top of the file. The
bitmap fonts in the font/luc, font/lucm, font/lucsans, and font/pelm
directory are copyright B&H Inc. and distributed under more restricted
terms under agreement with B&H.  See the NOTICE file in those directories.

Most of the COPYRIGHT, LICENSE, NOTICE and, or README informative files
are installed, but in /usr/local/plan9/unix or $PLAN9/unix directory."

--
Balwinder S "bdheeman" Dheeman        Registered Linux User: #229709
Anu'z Linux@HOME (Unix Shoppe)        Machines: #168573, 170593, 259192
Chandigarh, UT, 160062, India         Plan9, T2, Arch/Debian/FreeBSD/XP
Home: http://werc.homelinux.net/      Visit: http://counter.li.org/



  parent reply	other threads:[~2010-03-04 17:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.10536.1267643675.1513.9fans@9fans.net>
2010-03-03 20:22 ` EBo
2010-03-03 20:59   ` Jacob Todd
2010-03-04 17:39   ` Balwinder S Dheeman [this message]
2010-03-05  2:42   ` Andy Spencer
2010-03-05  2:53     ` erik quanstrom
2010-03-05 13:00     ` EBo
2010-03-05 13:30       ` EBo
2010-03-05 13:46         ` erik quanstrom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=tvv467x1fi.ln2@news.homelinux.net \
    --to=bsd.sanspam@cto.homelinux.net \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).