public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] questions about small fixes/cleanups
Date: Wed, 14 Sep 2016 15:21:35 +0200	[thread overview]
Message-ID: <20160914152135.3e4b547c@gentoo.org> (raw)
In-Reply-To: <8aa76e3e-0f4b-fbe1-1fbe-979abd25f957@gentoo.org>

On Wed, 14 Sep 2016 08:45:58 -0400
Michael Orlitzky <mjo@gentoo.org> wrote:

> On 09/14/2016 01:54 AM, Ulrich Mueller wrote:
> > 
> > We had a review of such files before the git conversion:
> > https://bugs.gentoo.org/550434
> > 
> > Especially, there's a list of "maintainer scripts" in comment #13.
> > At the time, we didn't do anything about them. There are very few of
> > such files (namely, 12 when that comment was written) so the space
> > taken by them is negligible.
> >   
> 
> I'll take the low hanging fruit:
> 
>   * dev-libs/collada-dom/files/take_snapshot.sh
>   * sys-libs/libcxxrt/files/prepare_snapshot.sh
> 
> Those two are completely trivial; clone a repo, rm -rf .git, tar it
> up.


Guess you never had to maintain packages whose releases are only
snapshots. They're trivial but it's a waste of time to re-assemble all
the bits every couple of months when you want to make a snapshot.

Questions one needs to answer:

- What SCM is used ?
- What is the URI ?
- How to fetch it ?
- What should be cleaned up after fetching ?
- What dirname to use so that it matches ebuilds' $S ?
- What compression to use so that it matches SRC_URI ?




Those scripts are made to automate this, and as you can see are closely
related to ebuilds, and thus fit perfectly next to them.


  reply	other threads:[~2016-09-14 13:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13 18:57 [gentoo-dev] questions about small fixes/cleanups Michael Mair-Keimberger
2016-09-13 19:21 ` M. J. Everitt
2016-09-13 23:25 ` Daniel Campbell
2016-09-13 23:49 ` Michael Orlitzky
2016-09-14  2:55   ` Kent Fredric
2016-09-14  5:54   ` Ulrich Mueller
2016-09-14 12:45     ` Michael Orlitzky
2016-09-14 13:21       ` Alexis Ballier [this message]
2016-09-14 13:38         ` Michael Orlitzky
2016-09-14 13:50           ` Alexis Ballier
2016-09-14 13:53             ` James Le Cuirot
2016-09-14 13:55               ` James Le Cuirot
2016-09-14 14:14                 ` Kent Fredric
2016-09-14 14:32                 ` Alexis Ballier
2016-09-14 14:04             ` Michael Orlitzky
2016-09-14 14:41               ` Alexis Ballier
2016-09-14 16:20                 ` Kent Fredric
2016-09-14 20:13                   ` Ian Stakenvicius
2016-09-19  7:51         ` Daniel Campbell
2016-09-19  7:55           ` Kristian Fiskerstrand
2016-09-19  8:00             ` Chí-Thanh Christopher Nguyễn
2016-09-19 10:06               ` Kristian Fiskerstrand
2016-09-19  8:26           ` Alexis Ballier

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=20160914152135.3e4b547c@gentoo.org \
    --to=aballier@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