From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] package.mask vs ~arch
Date: Sun, 6 Jul 2014 14:30:32 -0500 [thread overview]
Message-ID: <20140706193032.GA27048@linux1> (raw)
In-Reply-To: <53B94A06.1070907@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 699 bytes --]
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
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2014-07-06 19:30 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 4:01 [gentoo-dev] package.mask vs ~arch William Hubbs
2014-06-30 6:04 ` Alexandre Rostovtsev
2014-06-30 18:51 ` [OT] " Tom Wijsman
2014-06-30 8:12 ` Andreas K. Huettel
2014-06-30 18:57 ` Tom Wijsman
2014-06-30 11:29 ` hasufell
2014-06-30 14:11 ` Alexandre Rostovtsev
2014-06-30 14:37 ` Rich Freeman
2014-06-30 15:27 ` Jeroen Roovers
2014-06-30 19:49 ` Joshua Kinard
2014-06-30 20:36 ` Jeroen Roovers
2014-07-02 10:10 ` Peter Stuge
2014-06-30 13:25 ` Rich Freeman
2014-06-30 14:15 ` Jeroen Roovers
2014-06-30 14:48 ` Rich Freeman
2014-06-30 19:11 ` Tom Wijsman
2014-06-30 19:19 ` Rich Freeman
2014-07-02 17:56 ` Tom Wijsman
2014-07-02 18:04 ` Rich Freeman
2014-07-01 12:41 ` Patrick Lauer
2014-07-01 13:48 ` Rich Freeman
2014-07-05 21:08 ` Greg KH
2014-07-06 13:07 ` hasufell
2014-07-06 19:30 ` William Hubbs [this message]
2014-06-30 15:22 ` Ian Stakenvicius
2014-06-30 15:36 ` Michał Górny
2014-06-30 15:40 ` Ian Stakenvicius
2014-06-30 16:13 ` Jeroen Roovers
2014-06-30 16:32 ` William Hubbs
2014-06-30 17:07 ` Rich Freeman
2014-06-30 17:49 ` William Hubbs
2014-06-30 19:18 ` Tom Wijsman
2014-06-30 16:40 ` Rich Freeman
2014-06-30 16:55 ` Jeroen Roovers
2014-06-30 19:14 ` Tom Wijsman
2014-06-30 19:44 ` Ian Stakenvicius
2014-07-02 17:58 ` Tom Wijsman
2014-06-30 21:11 ` Roy Bamford
2014-06-30 20:01 ` Joshua Kinard
2014-06-30 20:50 ` Roy Bamford
2014-08-01 9:13 ` [gentoo-dev] " Steven J. Long
2014-08-01 15:19 ` William Hubbs
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=20140706193032.GA27048@linux1 \
--to=williamh@gentoo.org \
--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