| 1 |
On Tue, 2 Aug 2011 17:29:29 -0700 |
| 2 |
Brian Harring <ferringb@×××××.com> wrote: |
| 3 |
> On Tue, Aug 02, 2011 at 06:39:18PM +0100, Ciaran McCreesh wrote: |
| 4 |
> > On Tue, 02 Aug 2011 13:36:12 -0400 |
| 5 |
> > Jonathan Callen <abcd@g.o> wrote: |
| 6 |
> > > That statement needs one more qualification: "and doesn't use |
| 7 |
> > > portage". Portage will (by default) remove files on uninstall |
| 8 |
> > > even if they *do not* match the checksum recorded in the vdb. |
| 9 |
> > > This implies that most people will *not* see any issues due to |
| 10 |
> > > something other than the package manager modifying the files |
| 11 |
> > > behind the package manager's back. |
| 12 |
> > |
| 13 |
> > Ugh, seriously? When did that happen? That's a massive change to how |
| 14 |
> > VDB is supposed to work. |
| 15 |
> |
| 16 |
> That's been in place a long while; pkgcore has done it from day one |
| 17 |
> also. |
| 18 |
> |
| 19 |
> That's not a "massive change" to vdb behaviour either; file |
| 20 |
> collisions aren't supposed to occur, as such ownership of the file is |
| 21 |
> basically guranteed back to a single package. Throw in |
| 22 |
> CONFIG_PROTECT for adjusting the behaviour, and you have a far more |
| 23 |
> preferable norm than "lets just leave a shit ton of .pyc/.pyo on the |
| 24 |
> fs". |
| 25 |
|
| 26 |
It is a massive change, since if the feature is there then people don't |
| 27 |
feel bad about writing lousy pkg_ functions that leave a load |
| 28 |
of .pyc / .pyo files all over the place. |
| 29 |
|
| 30 |
-- |
| 31 |
Ciaran McCreesh |
Archives