public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org, gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-dev] Portage Sets
Date: Tue, 29 Aug 2006 07:57:43 -0400	[thread overview]
Message-ID: <44F42BB7.4010005@gentoo.org> (raw)

So I have implemented merging of sets (more or less) in a local portage
branch.  However there are some use cases for which the appopriate
action is ambiguous.

Use Case #1:
Set1 = { postfix, gentoolkit, lsof, bind-utils, vixie-cron }

A set of standard tools to be on a machine.  Assume a new install (ie
none of the packages in Set1 are installed).  Is it an error if one of
the packages in the set is masked or unavailable?  In this case I would
say yes; if you instead just skip the masked package (say postfix in
this case because it's convenient ) vixie-cron will pull ssmtp instead
of postfix.

Of course this will also occur if postfix is after vixie-cron in the
set; but for our purposes we will assume the administrator put them in
this order such that postfix will get pulled in.

One could also say that the user should have used emerge -pv set1 and
noticed that ssmtp is being pulled in instead of postfix.

Use Case #2:

Set1 = cat /var/lib/portage/world (the world set)

Assume the world file has 100 packages in it, two which are masked, and
three of which there are no ebuilds in the tree for.  If missing
packages cause an error (which in use case 1 they should imho) then the
user cannot update world without unmasking things properly.  The
packages for which ebuilds are missing in the tree is in fact a portage
bug(I think), and will probably need to be fixed.

Other use cases for sets would be appreciated, as far as behavior.  It
would probably be best to provide some sort of switch.

Unmerging sets is also a fun one, I'm not sure if it's entirely
appropriate yet.
-- 
gentoo-dev@gentoo.org mailing list



             reply	other threads:[~2006-08-29 12:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-29 11:57 Alec Warner [this message]
2006-08-29 14:22 ` [gentoo-dev] Portage Sets Kevin F. Quinn
2006-08-29 14:37   ` Chris White
2006-08-29 14:44     ` Simon Stelling
2006-08-29 17:41       ` Mike Frysinger
2006-08-29 18:22         ` Wernfried Haas
2006-08-29 18:42           ` Mike Frysinger
2006-08-29 16:22   ` Alec Warner
2006-08-29 15:04 ` Chris White
2006-08-29 15:25 ` Ciaran McCreesh
     [not found]   ` <44F471A5.3020405@gentoo.org>
2006-08-29 17:20     ` Ciaran McCreesh
2006-08-29 17:45   ` Mike Frysinger

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=44F42BB7.4010005@gentoo.org \
    --to=antarus@gentoo.org \
    --cc=gentoo-dev@lists.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