| 1 |
On Mon, 30 Apr 2012 11:40:26 +0200 |
| 2 |
Krzysztof Pawlik <nelchael@g.o> wrote: |
| 3 |
|
| 4 |
> On 30/04/12 11:30, Michał Górny wrote: |
| 5 |
> > On Mon, 30 Apr 2012 10:24:58 +0200 |
| 6 |
> > Krzysztof Pawlik <nelchael@g.o> wrote: |
| 7 |
> > |
| 8 |
> >> On 30/04/12 08:57, Michał Górny wrote: |
| 9 |
> >>> Hello, |
| 10 |
> >>> |
| 11 |
> >>> Since lately Gentoo devs force you to replace collision-protect |
| 12 |
> >>> with protect-owned [1] and sometimes packages just spit out files |
| 13 |
> >>> randomly on the filesystem due to random errors, I thought it may |
| 14 |
> >>> be a good idea to provide a new feature limiting the locations |
| 15 |
> >>> where packages can install. |
| 16 |
> >> |
| 17 |
> >> You're not forced to do anything. |
| 18 |
> > |
| 19 |
> > I am not? How come random ebuilds die in pkg_pretend() for me then? |
| 20 |
> > |
| 21 |
> >> |
| 22 |
> >>> In order to do that, we should first compose a complete |
| 23 |
> >>> include/exclude list where packages can install. I'd suggest the |
| 24 |
> >>> following: |
| 25 |
> >>> |
| 26 |
> >>> + /bin |
| 27 |
> >>> + /boot (but maybe just subdirectories so packages can't overwrite |
| 28 |
> >>> kernels?) |
| 29 |
> >>> [potentially + /dev? but that's useful only when tmpfs isn't |
| 30 |
> >>> mounted] |
| 31 |
> >>> + /etc |
| 32 |
> >>> + /lib, /lib32, /lib64 |
| 33 |
> >>> + /opt |
| 34 |
> >>> + /sbin |
| 35 |
> >>> [potentially + /service for ugly daemontools] |
| 36 |
> >>> + /usr |
| 37 |
> >>> + /var |
| 38 |
> >>> - /usr/local |
| 39 |
> >>> - /usr/portage |
| 40 |
> >>> |
| 41 |
> >>> What are your thoughts on this? |
| 42 |
> >>> |
| 43 |
> >>> [1]:https://bugs.gentoo.org/show_bug.cgi?id=410691#c4 |
| 44 |
> >> |
| 45 |
> >> I think it's feature creep - you can just set |
| 46 |
> >> INSTALL_MASK="/usr/local /usr/portage", no need for new features. |
| 47 |
> >> |
| 48 |
> >> PS. I (and few other folks) don't have /usr/portage. |
| 49 |
> > |
| 50 |
> > INSTALL_MASK won't make committing such an ebuild a fatal error. It |
| 51 |
> > will just hide problems. |
| 52 |
> |
| 53 |
> How would your proposed feature prevent ebuilds that install |
| 54 |
> something to /usr/local from being committed? |
| 55 |
|
| 56 |
If we enable this by default, devs will get errors for that. |
| 57 |
|
| 58 |
> Other valid case are private repos - I have a few ebuilds that |
| 59 |
> install stuff to /<some_random_dir> (proprietary stuff). |
| 60 |
|
| 61 |
Feel free to disable it. That's what FEATURES are for. |
| 62 |
|
| 63 |
-- |
| 64 |
Best regards, |
| 65 |
Michał Górny |
Archives