On 09/04/2018 10:58 AM, Michał Górny wrote:
> Add a check that verifies whether ebuilds don't install to paths
> forbidden by the policy. This mostly aims to verbosely report bugs
> such as missing dependencies causing empty install paths, resulting
> in files ending up in / and bad upstreams.
Add a check that verifies whether ebuilds don't install to paths
forbidden by the policy. This mostly aims to verbosely report bugs
such as missing dependencies causing empty install paths, resulting
in files ending up in / and bad upstreams. This should also help
detect the relatively common
On 09/04/2018 01:53 PM, Michał Górny wrote:
> + # TODO: do we need it? gconf installs empty dir there but that's
> + # all
> + root
FWIW, we should not allow this.
Add a check that verifies whether ebuilds don't install to paths
forbidden by the policy. This mostly aims to verbosely report bugs
such as missing dependencies causing empty install paths, resulting
in files ending up in / and bad upstreams. This should also help
detect the relatively common
On Tue, 2018-09-04 at 13:24 +0200, Ulrich Mueller wrote:
> > > > > > On Tue, 04 Sep 2018, Michał Górny wrote:
> > + # toplevel directories which can be installed to by ebuilds
> > + # /home is not included as no ebuilds should install files there
> > + local allowed_paths_toplevel=(
> > +
> On Tue, 04 Sep 2018, Michał Górny wrote:
> + # toplevel directories which can be installed to by ebuilds
> + # /home is not included as no ebuilds should install files there
> + local allowed_paths_toplevel=(
> + "${allowed_common_dirs[@]}"
> + boot dev
