From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Ebuild hacking howto
Date: Sat, 26 Feb 2011 08:28:02 +0000 [thread overview]
Message-ID: <201102260828.05801.michaelkintzios@gmail.com> (raw)
In-Reply-To: <AANLkTinUsjX0yWJwziJPfoUBh3z7gqv6sGTebgKtOXMG@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 948 bytes --]
On Saturday 26 February 2011 00:43:43 Mark Shields wrote:
> Saw that you linked to the "creating an updated ebuild" from gentoo-wiki,
>
> so what I say may overlay quite a bit, but hear me out:
>
> It depends on how the ebuild is built. If it references the version by the
> ebuild file name, which is very common, you can create an overlay for the
> ebuild, copy the ebuild to it, rename the ebuild file to have the new
> version number as part of it, digest the ebuild, make sure the overlay is
> listed in your make.conf file, then try to emerge it. I did this with
> Webmin. Yes, I know it's masked and new versions have effectively been
> dropped from portage; but I use it, and it worked fine.
Not related to the OP's question, but couldn't stop myself from asking:
Why is/was webmin dropped from portage?
I saw bug 348432 for webmin-1.530, but other than offering an ebuild it didn't
say.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-02-26 9:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 13:13 [gentoo-user] Ebuild hacking howto James
2011-02-25 13:41 ` [gentoo-user] " James
2011-02-25 15:35 ` [gentoo-user] " Michael Orlitzky
2011-02-26 0:43 ` Mark Shields
2011-02-26 8:28 ` Mick [this message]
2011-02-26 14:56 ` Dale
2011-02-26 16:28 ` Mick
2011-02-26 20:16 ` Marc Joliet
2011-02-28 1:43 ` Mark Shields
2011-02-28 1:53 ` Mike Gilbert
2011-02-28 15:45 ` [gentoo-user] " James
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=201102260828.05801.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@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