9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Taru Karttunen <taruti@taruti.net>
To: Ethan Grammatikidis <eekee57@fastmail.fm>, 9front@googlegroups.com
Subject: Re: package manager? seriously?
Date: Mon, 04 Apr 2011 08:24:29 +0300	[thread overview]
Message-ID: <87y63qk2r6.fsf@hydra.violetti.org> (raw)
In-Reply-To: <41D312FB-F15E-4DC5-8B8F-2EDEA44460A2@fastmail.fm>

On Mon, 4 Apr 2011 02:16:43 +0100, Ethan Grammatikidis <eekee57@fastmail.fm> wrote:
> Ugh. I'm tired, I've been writing and doing stuff far too much this  
> past week, and then people start bringing up "what's going to be  
> 9front's package manager" as if it were some kind of fait accompli,  
> and instantly talking about "how are we going to have the package  
> manager deal with config files?"

We already have a package manager by the name of contrib/install.

Do we want mercurial and hg as part of the base system?

If not we need a solution for installing (preferrably binary) versions
of them. Also a way of upgrading would be nice (re 9fans new hg version
thread). 

Do you think the current contrib way is any saner?

We *can* omit dependencies and config files totally from package
management.

All I am thinking of is:
+ copy files quickly over network
+ install avoiding clobbering local files
+ provide remove/upgrade
+ don't start with config file madness
+ don't do complex dependencies

ps. This started from #cat-v when I noted that some of my simple installer
code does work on Plan 9.

- Taru Karttunen

  reply	other threads:[~2011-04-04  5:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04  1:16 Ethan Grammatikidis
2011-04-04  5:24 ` Taru Karttunen [this message]
2011-04-04  6:04   ` Stanley Lieber
2011-04-04 11:37     ` Jacob Todd
2011-04-08 13:16 ` cinap_lenrek
2011-04-08 13:22   ` Jacob Todd

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=87y63qk2r6.fsf@hydra.violetti.org \
    --to=taruti@taruti.net \
    --cc=9front@googlegroups.com \
    --cc=eekee57@fastmail.fm \
    /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).