From: Kurt H Maier <khm@sciops.net>
To: 9front@9front.org
Subject: Re: [9front] Ports Tree utilities inclusion into 9front
Date: Wed, 28 Oct 2015 21:27:49 -0400 [thread overview]
Message-ID: <20151029012749.GC92033@wopr.sciops.net> (raw)
In-Reply-To: <78bee3eb1cb26a3e17ad321ffe042334@styx>
On Wed, Oct 28, 2015 at 09:03:52PM -0400, mveety@mveety.com wrote:
> Thats also a possiblity, but I would like a relationship similar to FreeBSD's or OpenBSD's
> ports tree. All the tools are in the OS to use it, but the tree isn't by default. Also I
> would like this to be a step towards removing shit (read acme) from the OS and shipping it
> in the ports tree.
I mean, why not put the tools in contrib and just have a ports script
that brings them into the users namespace. This keeps the ports tools
development out of the base system... which is what freebsd and openbsd
should have done to start with >:(
khm
next prev parent reply other threads:[~2015-10-29 1:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 1:03 mveety
2015-10-29 1:27 ` Kurt H Maier [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-10-29 17:57 mveety
2015-10-29 3:49 sl
2015-10-29 3:17 mveety
2015-10-28 22:50 mveety
2015-10-29 0:20 ` [9front] " Kurt H Maier
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=20151029012749.GC92033@wopr.sciops.net \
--to=khm@sciops.net \
--cc=9front@9front.org \
/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).