From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] Re: [RFC] New file layout for PKGDIR and binhosts
Date: Fri, 26 Dec 2014 05:20:35 +0000 (UTC) [thread overview]
Message-ID: <pan$4888$63244f0a$72391c2$fb2a7f9e@cox.net> (raw)
In-Reply-To: 549BEF34.90603@gentoo.org
Zac Medico posted on Thu, 25 Dec 2014 03:04:20 -0800 as excerpted:
> FWIW, you can use 'cp -rl $PKGDIR $PKGDIR.backup' to make a hardlink
> snapshot of $PKGDIR. Portage will break hardlinks whenever it needs to
> update tbz2 files, so you don't have to worry about updates in $PKGDIR
> affecting the files in $PKGDIR.backup.
Thanks. Your portage knowledge, and more to the point your calm patience
explaining its workings and fixing its bugs, always amaze me. =:^) I
sure missed it while you were gone and sure am glad you're back, with
more help now. =:^)
I had overlooked emaint --fix binhost (a hazard for those who have been
around long enough to have tools seriously evolve after the original
learning period), and hadn't thought at all about hardlinks (or btrfs
reflinks, since I'm using it for that partition). I expect I'll find
this quite useful. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-12-26 5:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-24 1:51 [gentoo-portage-dev] [RFC] New file layout for PKGDIR and binhosts Zac Medico
2014-12-24 5:16 ` Matthew Thode
2014-12-24 8:13 ` Zac Medico
2014-12-24 12:01 ` vivo75
2014-12-24 16:07 ` Zac Medico
2014-12-24 18:36 ` vivo75
2014-12-24 19:17 ` Zac Medico
2014-12-25 10:03 ` [gentoo-portage-dev] " Duncan
2014-12-25 11:04 ` Zac Medico
2014-12-26 5:20 ` Duncan [this message]
2015-01-07 5:32 ` Brian Dolbec
2014-12-27 14:25 ` [gentoo-portage-dev] " Rick "Zero_Chaos" Farina
2014-12-29 3:53 ` Zac Medico
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='pan$4888$63244f0a$72391c2$fb2a7f9e@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-portage-dev@lists.gentoo.org \
/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