9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: dante <subscriptions@posteo.eu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan9 Sources Repository
Date: Sat, 19 Jul 2014 17:06:26 +0200	[thread overview]
Message-ID: <033df8386d47dcbca83387af82fbc4a7@posteo.de> (raw)
In-Reply-To: <bc6b9ca42ba0156f2f4d9200517e009e@ladd.quanstro.net>

Hi Eric,

Thanks for your answers! They are really a good start for me with
Plan9.

So, you and the others convinced me that a source management system for
the main system is not really necessary.
What's left from my initial questions is if it won't be a bad idea to
have an integrated contrib (or packages) system.

Refined proposal:

1. Gather the good packages from the user's directories and other
sources on the net into a central system, like the core Plan9.
     There is some work implied to check licenses and get permissions.

2. Someone should filter the subsequent submissions, just the same as
with the core Plan9 (work:).
     If you guys don't like source control systems, let patch(1) be it.

3. Set up a maintenance routine for the whole package system, like
regular builds on all architectures, not to speak of automated tests.
     Packages that fall out of the maintenance routine shall be removed
after a while.

4. What could also happen in the long run is that some software is
ported from POSIX/Ape/X11 to the native Plan9 interfaces.

What do you think, 9fans?

On 19.07.2014 16:41, erik quanstrom wrote:
> given your questions, i am wondering if you have spent much time with
> the system.  especially one with history enabled.

Sincerely: no. That's homework.

Kind Regards,
Dante



  reply	other threads:[~2014-07-19 15:06 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 13:19 dante
2014-07-18 14:14 ` Aram Hăvărneanu
2014-07-18 14:18 ` cam
2014-07-18 14:36 ` erik quanstrom
2014-07-19  9:31   ` dante
2014-07-19 11:20     ` Riddler
2014-07-19 11:50       ` dante
2014-07-19 11:49     ` pmarin
2014-07-19 11:51       ` dante
2014-07-19 12:02         ` dante
2014-07-19 19:06           ` Anthony Sorace
2014-07-20  0:12           ` Brian L. Stuart
2014-07-20  7:33             ` dante
2014-07-19 12:03       ` tlaronde
2014-07-19 12:12         ` dante
2014-07-19 14:41     ` erik quanstrom
2014-07-19 15:06       ` dante [this message]
2014-07-19 15:11         ` Jacob Todd
2014-07-19 15:49           ` dante
2014-07-19 18:00             ` Kurt H Maier
2014-07-19 23:19               ` Brian L. Stuart
2014-07-19 18:17             ` erik quanstrom
2014-07-19 19:20               ` Christopher Nielsen
2014-07-19 20:13                 ` Aram Hăvărneanu
2014-07-19 22:10               ` dante
2014-07-19 22:30                 ` erik quanstrom
2014-07-20  7:33                   ` dante
2014-07-19 22:54                 ` Brian L. Stuart
2014-07-19 17:31         ` hiro
2014-07-19 17:48           ` dante
2014-07-19 15:03     ` Aram Hăvărneanu

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=033df8386d47dcbca83387af82fbc4a7@posteo.de \
    --to=subscriptions@posteo.eu \
    --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).