Jason Stubbs [EMAIL PROTECTED] wrote:
On Friday 08 July 2005 16:40, Craig Lawson wrote:
What I'd like to see *before* I upgrade is a list of advisories about
what trouble I'm in for.
How about the ChangeLog?
That would be a great answer. I look for trips and traps by doing an
`emerge
Zac Medico [EMAIL PROTECTED] wrote:
The attached patch for bug #132355 [1] adds a --mindeps option for
emerge that effectively allows build time dependencies to be excluded
from dependency calculations involving binary and installed packages.
With this patch, it's possible to remove all build
Brian Harring [EMAIL PROTECTED] wrote:
On Mon, Jul 31, 2006 at 07:42:23PM +0200, Marius Mauch wrote:
Was just brought to my attention that the =* operator doesn't work
as I thought, as for example =foo-1.2* matches foo-1.20 as well as
foo-1.2.3.
snip
but I'd suspect that many people share
Brian Harring [EMAIL PROTECTED] wrote:
On Mon, Jul 31, 2006 at 04:55:09PM -0700, Drake Wyrm wrote:
Brian Harring [EMAIL PROTECTED] wrote:
On Mon, Jul 31, 2006 at 07:42:23PM +0200, Marius Mauch wrote:
Was just brought to my attention that the =* operator doesn't
work as I thought
Mike Frysinger [EMAIL PROTECTED] wrote:
On Monday 31 July 2006 18:48, Brian Harring wrote:
Should be discussed on -dev, not here imo;
why ? short term we're gaining functionality:
simply add .*
Just making sure that I understand you... Given the original example
atom of =foo-1.2*, which
Mike Frysinger [EMAIL PROTECTED] wrote:
On Monday 31 July 2006 21:37, Drake Wyrm wrote:
Mike Frysinger [EMAIL PROTECTED] wrote:
short term we're gaining functionality: simply add .*
Just making sure that I understand you... Given the original example
atom of =foo-1.2*, which currently
Amit Dor-Shifer ami...@oversi.com wrote:
Hi.
In my overlay, I can have packages assigned to a private category, and
have that category specified in profiles/categories, under the overlay
itself.
However, in-order to ebuild such a package I have to append the category
to
