From: "Gabriel Diaz" <gabidiaz@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] plan9 packages
Date: Mon, 3 Sep 2007 08:22:44 +0200 [thread overview]
Message-ID: <82c890d00709022322p27d3d45fgfadcb02660713462@mail.gmail.com> (raw)
In-Reply-To: <5435f0cdbdf4b0a5a37db522519a0092@quintile.net>
hello
i think /contrib is the first step into this. May be we can build a
way to be able to replica/pull the /contrib dir, assume it would go in
/src/contrib or something like that, :-?
everyone can prepare its contributions to fit a common model (if that
is possible t :)
slds.
gabi
On 9/2/07, Steve Simon <steve@quintile.net> wrote:
> Hi,
>
> Can I suggest that when ken's fs is split from the main
> plan9 tree it is not tar'ed up but it is just copied to a source
> tree which contains only the kenfs stuff but in their correct places
> in a plan9 hierarchy, and a replica proto generated for it.
>
> The idea is that the new owner(s) of the kenfs tree could be given
> write permission to the code and then those who want to continue
> to use it could get the latest changes by doing somthing like:
>
> bind -a /n/sources/plan9/replica /n/sources/extra/kenfs/replica
> replica/pull kenfs
>
> We would lose nothing as the last "supported" release of kenfs will
> allways be available in sourcesdump.
>
> I would be willing to try to do the same work with some of the other
> tars in the contrib area (x11, tex etc)
>
> I do understand the danger that we might end up with somthing like the debian
> package managment stuff However it would be great to have an easy way to grab
> an arbitary package and keep it up to date. I recently fixed a silly bug in
> cvsfs but it doesn't really seem worthwhile emailing the whole list.
>
> It would also be great if the packages had some sport of Author file so
> people could submit patches against them and the relevant person/people would
> get the patch email.
>
> What do people think, neat idea or the thin end of the wedge?
>
> -Steve
>
prev parent reply other threads:[~2007-09-03 6:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-02 11:28 Steve Simon
2007-09-03 6:22 ` Gabriel Diaz [this message]
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=82c890d00709022322p27d3d45fgfadcb02660713462@mail.gmail.com \
--to=gabidiaz@gmail.com \
--cc=9fans@cse.psu.edu \
/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).