From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] nupas update
Date: Sun, 16 May 2010 21:09:02 -0700 [thread overview]
Message-ID: <AANLkTineyyQsinFWiKm83CdH0LmFYZOPy32ECEa_r5GF@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinBQjE7JQ_yFigQkBO-jd4SOiRseLZYoCrPloON@mail.gmail.com>
On Sun, May 16, 2010 at 6:35 PM, Akshat Kumar
<akumar@mail.nanosouffle.net> wrote:
> Is `rbind' a recursive bind, that takes care of binding at
> all depths? Because that's what you'd need in order
> for the binds to work. And then you shouldn't have any
> problems.
Yes, aki wrote it and yes, I thought it should solve the problems. It
did not seem to work.
I'll get you a copy. Oh wait look here.
http://9grid.net/magic/webls?dir=/aki/src/cmd
i sure do miss aki. Can you try the rbind thing and see if I got
something wrong? Would be *very* nice to leave the files in the .iso
and just bind things.
> If I can come up with a general set of commands to revert
> a given package à la history(1)/yesterday(1), I would put
> a set of those commands in /installed/$i when the package
> is installed. Then you just pass it to rc and you're golden.
I don't think that's good enough. It's fine for standalone packages.
But consider hg. It depends on 3 or 4 things. Should you track that
stuff too, and not remove python is hg is installed? If python creates
'x', and hg creates 'x', should you remove x if you remove HG? and so
on ... This is what makes tracking packages so ugly.
It gets ugly fast. I would just as soon mount the .iso's and do binds.
ron
next prev parent reply other threads:[~2010-05-17 4:09 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 2:16 erik quanstrom
2009-09-03 2:29 ` David Leimbach
2009-09-03 2:37 ` erik quanstrom
2010-05-15 23:17 ` Akshat Kumar
2010-05-15 23:45 ` erik quanstrom
2010-05-16 2:36 ` ron minnich
2010-05-16 4:15 ` erik quanstrom
2010-05-16 4:28 ` Akshat Kumar
2010-05-16 4:35 ` ron minnich
2010-05-16 4:39 ` erik quanstrom
2010-05-16 4:51 ` ron minnich
2010-05-16 4:57 ` Akshat Kumar
2010-05-16 5:44 ` ron minnich
2010-05-16 13:42 ` EBo
2010-05-16 14:03 ` erik quanstrom
2010-05-16 14:51 ` Ethan Grammatikidis
2010-05-16 15:37 ` EBo
2010-05-16 15:53 ` Ethan Grammatikidis
2010-05-16 16:02 ` ron minnich
2010-05-16 17:10 ` Ethan Grammatikidis
2010-05-16 17:19 ` EBo
2010-05-16 15:21 ` EBo
2010-05-16 15:42 ` Ethan Grammatikidis
2010-05-16 17:34 ` EBo
2010-05-16 17:47 ` hiro
2010-05-16 18:58 ` Corey
2010-05-16 19:29 ` EBo
2010-05-18 21:35 ` Georg Lehner
2010-05-18 22:07 ` ron minnich
2010-05-16 15:46 ` Jorden M
2010-05-16 15:59 ` Ethan Grammatikidis
2010-05-16 15:42 ` Jorden M
2010-05-16 18:24 ` erik quanstrom
2010-05-16 18:49 ` EBo
2010-05-16 20:44 ` erik quanstrom
2010-05-16 21:44 ` EBo
2010-05-17 1:17 ` erik quanstrom
2010-05-17 1:52 ` EBo
2010-05-17 1:58 ` erik quanstrom
2010-05-17 1:35 ` Akshat Kumar
2010-05-17 4:09 ` ron minnich [this message]
2010-05-17 4:19 ` erik quanstrom
2010-05-17 4:56 ` ron minnich
2010-05-18 23:50 ` Federico G. Benavento
2010-05-18 23:59 ` ron minnich
2010-05-19 0:40 ` Jorden M
2010-05-19 1:40 ` Robert Ransom
-- strict thread matches above, loose matches on Subject: below --
2009-08-06 15:23 erik quanstrom
2008-10-23 0:08 erik quanstrom
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=AANLkTineyyQsinFWiKm83CdH0LmFYZOPy32ECEa_r5GF@mail.gmail.com \
--to=rminnich@gmail.com \
--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).