public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Cc: "Michał Górny" <mgorny@gentoo.org>
Subject: [gentoo-portage-dev] [PATCH 0/3] INSTALL_MASK redesign, part I
Date: Sun, 22 May 2016 08:56:01 +0200	[thread overview]
Message-ID: <20160522065604.10593-1-mgorny@gentoo.org> (raw)

Hello, everyone.

As part of new GLEP effort, I'm working on improving INSTALL_MASK
support in Portage to make it cleaner and more featureful. Here's
the first set of commits resulting from this.

The previous implementation of INSTALL_MASK was done purely in bash.
Long story short, Portage removed all files matching one of INSTALL_MASK
patterns from the installation image.

My implementation is done purely as a filter in Python. The ebuild
configuration bits now generate final list of INSTALL_MASK. It is
afterwards used in vartree bits to filter files while checking for
collisions, merging and unmerging appropriately.

The major differences/improvements are:

* The files are actually left in image directory. Not that it makes any
  real difference but it is a bit cleaner and more like real mask this
  way.

* The pre-install "removing" output has been replaced by listing files
  with "###" zing in merging output (which means "not installed due
  to INSTALL_MASK").

* All masked files are now listed in vdb CONTENTS. Therefore, tools
  like app-portage/install-mask can now figure out to which packages
  masks were applied and rebuild them on mask changes appropriately.

* Mask exclusions are supported now. Which means you can do e.g.:
  INSTALL_MASK="/usr/share/locale -/usr/share/locale/foo".

* The code is now whitespace-safe. While patterns specified
  in INSTALL_MASK directly still can not contain spaces, pattern groups
  will be able to use them.

In a few days, I'll try to provide a part II that would implement
the actual mask groups. However, I may need some help adding support
for the configuration files.

I'm not touching PKG_INSTALL_MASK for now since it's harder and outside
of the scope of what I'm trying to achieve.



Michał Górny (3):
  portage.package.ebuild.config: Move FEATURES=no* handling there
  Move INSTALL_MASK handling into merging
  portage.dbapi.vartree: Support exclusions in INSTALL_MASK

 bin/misc-functions.sh                |  30 ----------
 pym/portage/dbapi/vartree.py         | 104 ++++++++++++++++++++++-------------
 pym/portage/package/ebuild/config.py |  10 ++++
 3 files changed, 76 insertions(+), 68 deletions(-)

-- 
2.8.3



             reply	other threads:[~2016-05-22  6:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-22  6:56 Michał Górny [this message]
2016-05-22  6:56 ` [gentoo-portage-dev] [PATCH 1/3] portage.package.ebuild.config: Move FEATURES=no* handling there Michał Górny
2016-06-12  7:19   ` Zac Medico
2016-06-12  7:28     ` Zac Medico
2016-06-12  9:33       ` Michał Górny
2016-05-22  6:56 ` [gentoo-portage-dev] [PATCH 2/3] Move INSTALL_MASK handling into merging Michał Górny
2016-05-22  8:14   ` Michał Górny
2016-05-22  8:21   ` [gentoo-portage-dev] [PATCH v2] " Michał Górny
2016-06-12  8:41     ` Zac Medico
2016-06-12  9:10     ` Zac Medico
2016-06-12  9:28       ` Michał Górny
2016-06-12  9:49         ` Zac Medico
2016-06-12 10:05           ` Michał Górny
2016-06-12 10:28             ` Zac Medico
2016-06-12 20:29     ` Zac Medico
2016-06-12 20:43       ` Zac Medico
2016-06-12 20:52         ` Zac Medico
2016-05-22  6:56 ` [gentoo-portage-dev] [PATCH 3/3] portage.dbapi.vartree: Support exclusions in INSTALL_MASK Michał Górny
2016-06-12  9:20   ` Zac Medico
2016-06-12  9:31     ` Michał Górny
2016-06-12  9:43       ` Zac Medico
2016-06-12 10:03         ` Michał Górny
2016-06-12 10:23           ` Zac Medico
2016-05-31 15:58 ` [gentoo-portage-dev] [PATCH 4/3] portage.package.ebuild.config: Support path groups from install-mask.conf Michał Górny
2016-06-10 21:50   ` Michał Górny

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=20160522065604.10593-1-mgorny@gentoo.org \
    --to=mgorny@gentoo.org \
    --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