From: Benjamin Ritcey <gentoo-dev@ritcey.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] procedure for simple ebuild updates
Date: Thu, 24 Jan 2002 18:22:42 -0500 [thread overview]
Message-ID: <3C509742.7050508@ritcey.com> (raw)
Hey all,
Just wondering what the procedure is for simple ebuild updates -- curl
and gaim just had new releases, but the ebuilds only needed to be copied
to the new rev number (e.g., "cp curl-7.9-r1.ebuild curl-7.9.3.ebuild")
- no tweeking needed (just needed to 'fetch' and 'digest' to make sure
it works).
Doesn't seem quite worthwhile to submit an ebuild that's already in
portage - it merely has a different name... There's also the fact that
I didn't write those ebuilds - don't want to appear to be snatching credit.
Thanks,
-b
next reply other threads:[~2002-01-24 23:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 23:22 Benjamin Ritcey [this message]
2002-01-25 16:18 ` [gentoo-dev] procedure for simple ebuild updates Grant Goodyear
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=3C509742.7050508@ritcey.com \
--to=gentoo-dev@ritcey.com \
--cc=gentoo-dev@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