public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in media-libs/x265: x265-1.0.ebuild ChangeLog x265-1.2.ebuild x265-0.8.ebuild
Date: Wed, 30 Jul 2014 09:38:16 +0000 (UTC)	[thread overview]
Message-ID: <pan$a78bc$5cf250f0$78c422d6$736518e4@cox.net> (raw)
In-Reply-To: CA+CSuAJNXgZ+LHT3AgPv6yQyJG-w-KdtxUiwhKc9Ey7eRtq0Eg@mail.gmail.com

Denis Dupeyron posted on Tue, 29 Jul 2014 07:58:26 -0600 as excerpted:

> [H]ere is what I was instructed to teach recruits back when I became a
> recruiter in 2006 or 2007, and what competent developers have been doing
> since even before I was a developer:
> 
> The package.mask file is only for temporary masking, even if more or
> less long term. Anything that should be permanently masked has no place
> in the tree. Live ebuilds should not be keyworded, reflecting the fact
> that the code they're pulling has not be tested for any architecture due
> to it being live. Moreover, live ebuilds should not be masked as this
> results in unnecessary cruft in the package.mask file.

Thanks.  That makes sense, tho it does conflict with "content-touchless" 
bumps from the live ebuild.

In the context of that policy and a content-touchless-bump goal, I 
suppose I'd script the bump, pulling keywords from the highest previous 
version, prepending the ~ as necessary and inserting them in the keywords 
line after copying the file from the live-ebuild .  That wouldn't be 
content-touchless, but the touch would be automated so as to avoid 
mistakes and unnecessary work.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman



  reply	other threads:[~2014-07-30  9:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140727190116.B09072004E@flycatcher.gentoo.org>
2014-07-28  6:41 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in media-libs/x265: x265-1.0.ebuild ChangeLog x265-1.2.ebuild x265-0.8.ebuild Samuli Suominen
2014-07-28  8:02   ` Samuli Suominen
2014-07-28 20:52     ` Markus Meier
2014-07-29  0:15   ` Denis Dupeyron
2014-07-29  0:49     ` Alex Xu
2014-07-29 13:33       ` Denis Dupeyron
2014-07-29  2:41     ` Duncan
2014-07-29 13:58       ` Denis Dupeyron
2014-07-30  9:38         ` Duncan [this message]
2014-07-30 11:48           ` Luis Ressel
2014-07-30 12:33             ` Samuli Suominen
2014-07-30 15:14               ` Luis Ressel
2014-07-30 17:29               ` Michael Haubenwallner
2014-07-30 17:33                 ` Samuli Suominen
2014-07-31  7:19                   ` Michael Haubenwallner
2014-07-30 20:15                 ` William Hubbs
2014-08-13  7:04             ` Tom Wijsman
2014-07-29 17:32     ` Samuli Suominen

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='pan$a78bc$5cf250f0$78c422d6$736518e4@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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