On Sun, Jul 06, 2014 at 01:07:18PM +0000, hasufell wrote: > If you are talking about actually testing and running the software then > that's a different story and definitely not within our scope when > committing to ~arch. > > That said, I think it's a reasonable minimum to at least check if an > ebuild emerges on my current machine with my current setup before > committing to ~arch. If even that fails, what's the point of committing > the ebuild?
Yes, this is basically what I do. I make sure the ebuild emerges and the software runs in the configuration I was running the old version in. Once I know that's true, I don't see anything wrong with committing to ~arch. William
signature.asc
Description: Digital signature
