From: Ned Ludd <solar@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] framework for local auto patching
Date: Sun, 24 Apr 2005 11:02:19 -0400 [thread overview]
Message-ID: <1114354939.27596.47.camel@localhost> (raw)
The dev-portage@ guys will probably hate me for telling the rest of you
this kinda framework is even remotely possible but I'm sure they will
get over it.. (hi ferringb)
If your like me and have a rather large customized overlay to apply misc
patches to misc packages that really don't change much at the source
level and your getting sick of the repetitive task of having to hawk
your overlay and make sure that it's ebuilds are kept up to date by
being >= than what $PORTDIR provides this might be just thing you
always needed.
http://dev.gentoo.org/~solar/portage_misc/bashrc.autopatch
Then simply do something like this.
cvs diff
> /var/cvsroot/gentoo-x86/local/patches/sys-apps/sandbox/sandbox-1.2.1-sfperms.patch
emerge sandbox
# where /var/cvs/gentoo-x86/local/patches is equiv to your desired auto
PATCH_OVERLAY
have fun.
--
Ned Ludd <solar@gentoo.org>
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2005-04-24 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-24 15:02 Ned Ludd [this message]
2005-04-24 17:08 ` [gentoo-dev] framework for local auto patching Georgi Georgiev
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=1114354939.27596.47.camel@localhost \
--to=solar@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