From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] rfc: versionator.eclass
Date: Sun, 5 Sep 2004 23:23:01 +0100 [thread overview]
Message-ID: <20040905232301.40a6387c@snowdrop.home> (raw)
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
Here's a little eclass I wrote the other day while out duck hunting
with a judge:
http://dev.gentoo.org/~ciaranm/tmp/versionator.eclass
The idea is to make it easier for people to get rid of a load of those
nasty global scope sed / cut calls. Actually, I lied. The idea is to
stop people from pestering me at 3am asking how to replace the second
hyphen with an underscore.
You could, of course, write a load of bash voodoo like certain ebuilds
do already. This leads to headaches though, especially when people get
it wrong...
Any use? Worth committing? I've got a few things that currently do bash
magic that could be converted over for readability purposes, and I know
others are in a similar situation...
Suggestions welcomed, especially if they come with patches.
--
Ciaran McCreesh : Gentoo Developer (Sparc, MIPS, Vim, Fluxbox)
Mail : ciaranm at gentoo.org
Web : http://dev.gentoo.org/~ciaranm
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2004-09-05 22:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040905232301.40a6387c@snowdrop.home \
--to=ciaranm@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