From: Christopher Schwan <cschwan@students.uni-mainz.de>
To: <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Opportunities to use slot operators
Date: Mon, 15 Apr 2013 11:39:12 +0200 [thread overview]
Message-ID: <2047118.lrJGOsM85g@cschwan-laptop> (raw)
In-Reply-To: <CAGfcS_nPNnrUvCg29xOn_HxyNR_A84Pa_isSNFrTCq8wUsSCeg@mail.gmail.com>
On Sunday 14 April 2013 09:09:13 Rich Freeman wrote:
> For whoever is interested I tossed together a script to identify
> packages that would immediately benefit from slot operator
> dependencies but which are not doing so.
>
> The list can be found at:
> http://dev.gentoo.org/~rich0/missedslotops.txt
>
> This was generated by:
> https://github.com/rich0/finddepslotops
>
> Feel free to make use of either as you see fit, make improvements,
> submit improvements, fork, whatever. If one of your packages is on
> the list feel free to update it! (And yes, I realize that in many
> cases this may have been done with newer versions of the packages not
> on the list - I didn't make any attempts to filter that out.)
>
> Also, I'm sure I've used the portage API in less-than-ideal ways.
> Having not really used it before this was half a learning exercise.
> Feel free to send me suggestions/pointers. If somebody knows of an
> easy way to process metadata in python (short of just parsing the xml
> myself) let me know - I didn't see any kind of API for that.
>
> Rich
Is it possible to check a local overlay? Specifying CPV for a single ebuild
works, but I wonder if its possible to parse an entire overlay at once.
Christopher
next prev parent reply other threads:[~2013-04-15 9:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-14 13:09 [gentoo-dev] Opportunities to use slot operators Rich Freeman
2013-04-14 13:23 ` [gentoo-dev] " Michael Palimaka
2013-04-14 17:11 ` [gentoo-dev] " Andreas K. Huettel
2013-04-14 20:59 ` Zac Medico
2013-04-15 9:39 ` Christopher Schwan [this message]
2013-04-15 11:30 ` Rich Freeman
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=2047118.lrJGOsM85g@cschwan-laptop \
--to=cschwan@students.uni-mainz.de \
--cc=gentoo-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