From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9front@googlegroups.com
Subject: package manager? seriously?
Date: Mon, 4 Apr 2011 02:16:43 +0100 [thread overview]
Message-ID: <41D312FB-F15E-4DC5-8B8F-2EDEA44460A2@fastmail.fm> (raw)
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?"
I think martian67 helped me organize my thoughts best when he said
"packages enforce a certain structure on things." ... I don't if this
will come across in text but what I really wanted to reply to that is
"Oh! OH!! Ohhh yeeesss, let's ENFORCE STRUCTURE!!! STRUCTURE is
GOOOOOOOD! Must have STRUCTURE!"
Plan 9's design is extremely good at making structure work in good,
useful, non-limiting ways. What's the system which makes the most use
of package management today? Gnu/Linux. What's the one system which
employs structure in the very worst way possible throughout? Gnu/Linux.
Package managers are a big part of the disease. Dependency tracking
helps create the longest and most brittle dependency chains. Config
file management isn't management at all. Either you are managing the
config files on your system or something else is, which way is it
going to go?
Another big argument is package managers somehow stop things making a
mess all over your system. Er, no, they provide a way for people to
patch random shit to fit an arbitrary structure... Is "random shit"
even remotely relevant in the context of 9front? For fuck's sake how
much bullshit are we going to pile on this OS anyway? Without, you
know, making it fit the OS first? Good grief people, THINK already.
Finally... "ohmigosh but the ONLY way you can possibly uninstall
cleanly is with a package manager" argument, to which I will reply
with two words: make uninstall. Plan 9 mkfiles already have all the
files they install listed, it shouldn't be hard to put an uninstall
target in the files every mkfile sources. This isn't random bullshit
made to work with crappy implementations of make, this is something
for which we can make an uninstall target work already.
For those STILL in fucking lust with package managers, will you
PLEASE stop thinking of 9front as a suitable platform for megalithic
dinosaurian monstrosities?
next reply other threads:[~2011-04-04 1:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 1:16 Ethan Grammatikidis [this message]
2011-04-04 5:24 ` Taru Karttunen
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=41D312FB-F15E-4DC5-8B8F-2EDEA44460A2@fastmail.fm \
--to=eekee57@fastmail.fm \
--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).