public inbox for gentoo-pms@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <gentoo@mgorny.alt.pl>
To: gentoo-pms@lists.gentoo.org
Subject: [gentoo-pms] (Minimal) standarization of the 'sets' feature
Date: Thu, 10 Jun 2010 15:42:38 +0200	[thread overview]
Message-ID: <20100610154238.45ad9de2@pomiocik.lan> (raw)

[-- Attachment #1: Type: text/plain, Size: 1897 bytes --]

Hello,

First of all, I would like to notice I'm not trying to force moving
Portage-specific features to PMS. I'm just trying to get some
standarization on one of these features to make it possible for devs to
use it in gx86 without commiting non-standard files.

The particular feature I'm talking about is defining repository-wide
package sets. Currently, this is done through a Portage-specific
'sets.conf' file in the repository's root directory. Although such file
could be considered acceptable for an overlay, I wouldn't like to see
such a non-standard file commited to gx86.

On the other hand, many of current Portage users could benefit from
the 'x11-module-rebuild' set we have introduced in 'x11' overlay [1].
This particular set quickly aggregates all X11 modules for a rebuild
after the xorg-server ABI change.

Portage by default supplies a few more sets which would fit repository-
-specific set definition file better than the system-wide Portage
configuration directory -- like the @live-rebuild and @module-rebuild
sets.

This is why I suggest considering adding some basic definitions
for 'sets' in the PMS, keeping that feature fully optional for PMs but
preparing a standarized ground for those who would like to use it.

What I would like to see in the PMS is:
1) a definition of a 'set',
2) a definition of few basic types of sets (Portage currently describes
them using specific classes but portable names would be much better),
3) a specification for repository-wide sets definition file.

In fact, the specification doesn't really even need to push the 'sets'
into atom specifications -- as I guess we would rather keep away from
using them in dependencies, and PM could be free to use any syntax to
reference them.

[1] http://tnij.org/g6rl

-- 
Best regards,
Michał Górny

<http://mgorny.alt.pl>
<xmpp:mgorny@jabber.ru>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2010-06-10 13:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-10 13:42 Michał Górny [this message]
2010-06-10 13:51 ` [gentoo-pms] (Minimal) standarization of the 'sets' feature Ciaran McCreesh
2010-06-10 14:18   ` Michał Górny
2010-06-10 17:19 ` Maciej Mrozowski

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=20100610154238.45ad9de2@pomiocik.lan \
    --to=gentoo@mgorny.alt.pl \
    --cc=gentoo-pms@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