From: Casey Allen Shobe <lists@seattleserver.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] ebuild development (vpopmail, etc.)
Date: Mon, 18 Jul 2005 04:26:03 +0000 [thread overview]
Message-ID: <200507180426.03638.lists@seattleserver.com> (raw)
Hi everyone,
I'm planning to edit the vpopmail ebuild Real Soon Now to add the
mysteriously missing postgres USE flag and thus end up with a
package compiled with the support we need.
Instead of wasting my time re-adding this every time a new version
of vpopmail comes along, I'd much rather use this as an opportunity
to get into Gentoo development and add this to the central ebuild
repository so that all future versions inherit it.
What do I need to do to get started on this? Do I simply mail a
patch to this list, or ask somebody for a CVS account and commit
changes directly?
I'm also a bit confused about the portdir_overlay thing - If there
exists a -r15, do I then add a -r16 to make emerge realize an
update is available. What happens then when an -r16 hits the
regular portage tree?
Thanks for any information you can provide.
Cheers,
--
Casey Allen Shobe | http://casey.shobe.info
cshobe@seattleserver.com | cell 425-443-4653
AIM & Yahoo: SomeLinuxGuy | ICQ: 1494523
SeattleServer.com, Inc. | http://www.seattleserver.com
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2005-07-18 4:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 4:26 Casey Allen Shobe [this message]
2005-07-18 5:07 ` [gentoo-dev] ebuild development (vpopmail, etc.) Anthony Gorecki
2005-07-18 6:57 ` Donnie Berkholz
2005-07-18 7:13 ` Anthony Gorecki
2005-07-18 7:25 ` Georgi Georgiev
2005-07-18 18:13 ` Casey Allen Shobe
2005-07-19 1:19 ` [gentoo-dev] " Duncan
2005-07-18 5:14 ` [gentoo-dev] " Alin Nastac
2005-07-18 13:19 ` Chris Gianelloni
2005-07-18 18:19 ` Casey Allen Shobe
2005-07-18 18:27 ` Jonathan Smith
2005-07-18 19:46 ` Chris Gianelloni
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=200507180426.03638.lists@seattleserver.com \
--to=lists@seattleserver.com \
--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