public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Roy Bamford <neddyseagoon@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] package.mask vs ~arch
Date: Mon, 30 Jun 2014 22:11:19 +0100	[thread overview]
Message-ID: <1404162701.1680.1@NeddySeagoon_Static> (raw)
In-Reply-To: <53B184E3.5040902@gentoo.org> (from axs@gentoo.org on Mon Jun 30 16:40:19 2014)

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

On 2014.06.30 16:40, Ian Stakenvicius wrote:
> On 30/06/14 11:36 AM, Michał Górny wrote:

[snip]

> >
> > But... if you unmask it, someone will test it and report whether
> > it works :P.
> >
> 
> But... if I unmask it, -everyone- using ~arch will install it and
> it'll break all the systems that it doesn't work on, which -could- be
> quite a lot at this point.  :D
> 
> 
> 

Yep.  The good old days ... X11 going modular ... expat-2 and a few 
others that I've forgotten.
There was no news then so if you missed an email to the list you got to 
pick up the pieces.  Those examples may well be me missing emails.

I've run ~arch since mid 2002 and until the last few years always had a 
few builds fail or things build then operate so badly they needed to be 
p.masked locally.  That's what buildpkg is for ... so that after you 
spend 10 hours building *office and find out its a dud, you can back it 
out in a few minutes.

-- 
Regards,

Roy Bamford
(Neddyseagoon) a member of
elections
gentoo-ops
forum-mods
trustees

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2014-06-30 21:12 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
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 [this message]
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=1404162701.1680.1@NeddySeagoon_Static \
    --to=neddyseagoon@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