[pkgcore] #175: Support per-repository sets
pkgcore
--------------------------------------+-------------------------------------
Reporter: sput...@quassel-irc.org | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: 0.4.5
Component: pkgcore | Version: 0.4.5
Keywords: |
--------------------------------------+-------------------------------------
Currently, at least judging from the docs, only one location for
specifying custom sets is supported (/etc/portage/sets). Since often, sets
are repository-specific, it should be possible to define and use sets
defined in overlays. Portage sorta does this (you can put a sets.conf in
the overlay root) already, though it's not fully working yet and still
work in progress, afaiu.
Extra bonus points for making the sets configuration compatible to
portage.
--
Ticket URL: <http://www.pkgcore.org/trac/pkgcore/ticket/175>
pkgcore <http://www.pkgcore.org/trac/pkgcore>
pkgcore package manager
pkgcore
---------------------------------------+------------------------------------
Type: enhancement | Status: new
Priority: normal | Milestone:
Resolution: | Keywords:
---------------------------------------+------------------------------------
Changes (by ferringb):
* milestone: 0.4.5 =>
Comment:
Propose something please;
re: sets.conf in the repo, realistically supporting that is going to be a
massive pita due to the fact it's portage specific namespace- meaning I'll
have to maintaining mappings indefinitely. Need to take that one up w/
genone...
--
Ticket URL: <http://www.pkgcore.org/trac/pkgcore/ticket/175#comment:1>
pkgcore
---------------------------------------+------------------------------------
Priority: normal | Milestone:
Resolution: | Keywords:
---------------------------------------+------------------------------------
Changes (by ArneBab):
* cc: arne_bab@… (added)
* version: 0.4.5 => 0.5.11.7
Comment:
Do you have any updates on this?
With kde4, per-repository sets have effectively become necessary for me to
do my kde updates, since the kde overlay uses them instead of meta ebuilds
to specify KDE development versions.
So currently I do my security updates (daily) with pkgcore, while I do the
KDE updates with portage.
--
Ticket URL: <http://www.pkgcore.org/trac/pkgcore/ticket/175#comment:2>
pkgcore
---------------------------------------+------------------------------------
Priority: normal | Milestone:
Resolution: | Keywords:
---------------------------------------+------------------------------------
Comment (by ferringb):
per repository sets are very portage specific last time I looked at them,
which makes them rather... undesirable... to support for pkgcore. I'm
open to per repo sets, but what is in place right now needs to be a fair
bit more manager agnostic- further, the repo needs to be watermarked in
some fashion so that it can be identified as a non pms repo (we need the
same thing for some overlaying package.masking repo wise).
--
Ticket URL: <http://www.pkgcore.org/trac/pkgcore/ticket/175#comment:3>
pkgcore
---------------------------------------+------------------------------------
Priority: normal | Milestone:
Resolution: | Keywords:
---------------------------------------+------------------------------------
Comment (by ArneBab):
Is there an alternate way for overlays to add sets?
I think the most important part for the overlay managers is to have a very
easy way to add sets. Up till a few minutes ago I thought people would
just have to add the sets dir with world-file-style plaintext files (till
I discovered the sets.conf with class=portage.… in the kde overlay).
For me, not having overlay sets really hurts, because I manage my whole
KDE install via the sets from the kde overlay.
--
Ticket URL: <http://www.pkgcore.org/trac/pkgcore/ticket/175#comment:4>