Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: "Paweł Hajdan, Jr." <phajdan.jr@g.o>
Subject: Re: RFC: More versatile return codes for emerge
Date: Wed, 25 Jan 2012 21:04:19 +0100
On 1/25/12 10:23 AM, Thomas Kahle wrote:
> I suggest that emerge could signal its various failures via return
> codes.  That would be useful in automated archtesting:
> 
> https://bugs.gentoo.org/show_bug.cgi?id=400705

My opinion is very similar to what Brian Harring said on that bug: some
Python API would be much better than still pretty vague return code
(what would you do with it?).

Some ideas:

- I emerge a list of packages, some unstable dependencies are required;
allow me to get a list of those package atoms

- same as above, but return list of USE flags adjustments required

- package blocks

- unsatisfied USE flag constraints

... and so on. I think it can start very simple and small, and be
extended as needed.

Attachment:
signature.asc (OpenPGP digital signature)
Replies:
Re: RFC: More versatile return codes for emerge
-- Thomas Kahle
References:
RFC: More versatile return codes for emerge
-- Thomas Kahle
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
RFC: More versatile return codes for emerge
Next by thread:
Re: RFC: More versatile return codes for emerge
Previous by date:
Re: How to handle x86/amd64 only packages on other arches
Next by date:
Re: How to handle x86/amd64 only packages on other arches


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.