public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Cc: Toha <tonich@e-diva.ru>
Subject: Re: [gentoo-portage-dev] files in ${FILESDIR}
Date: Tue, 5 May 2009 02:34:48 -0400	[thread overview]
Message-ID: <200905050234.49299.vapier@gentoo.org> (raw)
In-Reply-To: <20090505102621.55ffa379@tonich.warlock.ru>

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

On Tuesday 05 May 2009 02:26:21 Toha wrote:
> What about this idea: list all files in ${FILESDIR} (patches, init
> scripts), related to ebuild in this ebuild like:
>
> FLS=( "some-init-script" "${PN}-patch1.patch" "${PN}-${PV}-patch2.patch"
> ... "${PN}-patchN.patch" )
>
> then using this files by addressing his index in ${FLS} array
>
> applying patches with command: epatch 1 ( or in batch mode: epatch 1 2 3 )
> and init scripts like: doinitd 0
> etc.
>
> reason: easy automated way to moving ebuilds with all required files betwen
> repositories/overlays

downsides: updating of array causes ugly cascading of changes throughout the 
entire ebuild instead of one or two lines.  maintaining the info indirectly 
with numbers makes reading ebuilds harder to understand and harder to maintain 
(adding/dropping files).

such changes should be proposed on the gentoo-dev mailing list anyways ... 
you'll get a lot more feedback as to why this is more "con" than "pro".
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2009-05-05  6:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 12:23 [gentoo-portage-dev] Portage and SIGHUP Fabian Groffen
2009-04-23 17:52 ` Zac Medico
2009-05-05  6:26   ` [gentoo-portage-dev] files in ${FILESDIR} Toha
2009-05-05  6:34     ` Mike Frysinger [this message]

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=200905050234.49299.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    --cc=tonich@e-diva.ru \
    /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