From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: POSIX capability in Gentoo
Date: Wed, 3 Aug 2011 12:34:21 +0100 [thread overview]
Message-ID: <20110803123421.75bb6bde@googlemail.com> (raw)
In-Reply-To: <20110803002929.GA351@localhost>
[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]
On Tue, 2 Aug 2011 17:29:29 -0700
Brian Harring <ferringb@gmail.com> wrote:
> On Tue, Aug 02, 2011 at 06:39:18PM +0100, Ciaran McCreesh wrote:
> > On Tue, 02 Aug 2011 13:36:12 -0400
> > Jonathan Callen <abcd@gentoo.org> wrote:
> > > That statement needs one more qualification: "and doesn't use
> > > portage". Portage will (by default) remove files on uninstall
> > > even if they *do not* match the checksum recorded in the vdb.
> > > This implies that most people will *not* see any issues due to
> > > something other than the package manager modifying the files
> > > behind the package manager's back.
> >
> > Ugh, seriously? When did that happen? That's a massive change to how
> > VDB is supposed to work.
>
> That's been in place a long while; pkgcore has done it from day one
> also.
>
> That's not a "massive change" to vdb behaviour either; file
> collisions aren't supposed to occur, as such ownership of the file is
> basically guranteed back to a single package. Throw in
> CONFIG_PROTECT for adjusting the behaviour, and you have a far more
> preferable norm than "lets just leave a shit ton of .pyc/.pyo on the
> fs".
It is a massive change, since if the feature is there then people don't
feel bad about writing lousy pkg_ functions that leave a load
of .pyc / .pyo files all over the place.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-08-03 11:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-31 14:43 [gentoo-dev] POSIX capability in Gentoo Anthony G. Basile
2011-07-31 19:46 ` Nirbheek Chauhan
2011-07-31 20:00 ` Anthony G. Basile
2011-08-02 7:08 ` Michał Górny
2011-08-02 14:28 ` Anthony G. Basile
2011-08-02 14:31 ` Ciaran McCreesh
2011-08-02 14:51 ` Anthony G. Basile
2011-08-02 14:54 ` Ciaran McCreesh
2011-08-02 15:05 ` Anthony G. Basile
2011-08-02 15:05 ` Ciaran McCreesh
2011-08-02 15:19 ` Anthony G. Basile
2011-08-02 15:20 ` Ciaran McCreesh
2011-08-02 17:11 ` [gentoo-dev] " Duncan
2011-08-02 17:17 ` Ciaran McCreesh
2011-08-02 17:36 ` Jonathan Callen
[not found] ` <20110802173846.AF04F21C12C@pigeon.gentoo.org>
2011-08-02 17:39 ` Ciaran McCreesh
2011-08-02 20:46 ` Arfrever Frehtes Taifersar Arahesis
2011-08-03 1:19 ` Duncan
2011-08-03 0:29 ` Brian Harring
2011-08-03 11:34 ` Ciaran McCreesh [this message]
2011-08-03 21:26 ` Brian Harring
2011-08-03 21:28 ` Ciaran McCreesh
2011-08-03 21:52 ` Brian Harring
2011-08-02 15:15 ` [gentoo-dev] " Rich Freeman
2011-08-02 15:09 ` Michał Górny
2011-07-31 20:28 ` Michał Górny
2011-07-31 20:27 ` Ciaran McCreesh
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=20110803123421.75bb6bde@googlemail.com \
--to=ciaran.mccreesh@googlemail.com \
--cc=gentoo-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