From: "Stanley Lieber" <stanley.lieber@gmail.com>
To: 9front@googlegroups.com
Subject: Re: package manager? seriously?
Date: Mon, 4 Apr 2011 01:04:04 -0500 [thread overview]
Message-ID: <7d18540181b614f80fa21beb00091ad1@stanleylieber.com> (raw)
In-Reply-To: <87y63qk2r6.fsf@hydra.violetti.org>
> 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
fgb has also expressed interesting in a replacement for contrib.
One of the problems with contrib is the reliance on /n/sources
as the central repository. sources is slow, it depends on the continued
goodwill of the Labs for its existence, and there is no provision for fetching
files from alternate locations.
OpenBSD's ports system may be a good source of inspiration.
-sl
next prev parent reply other threads:[~2011-04-04 6:04 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
2011-04-04 6:04 ` Stanley Lieber [this message]
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=7d18540181b614f80fa21beb00091ad1@stanleylieber.com \
--to=stanley.lieber@gmail.com \
--cc=9front@googlegroups.com \
/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).