public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Zubkov <green@area-b.msu.ru>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] portage idea - auto embed user patches
Date: Thu, 21 Dec 2006 17:32:41 +0300	[thread overview]
Message-ID: <458A9B09.7070804@area-b.msu.ru> (raw)

Hi!
I have some idea on extending portage building system (ebuild?).
Sometimes I'm (for example) want to apply custom patch to some package.
This patch can do something unusual, that can not be accepted by
maintainers and I know this. But I like features in my patch and want it
to apply automatically when updating the package. Not to do it like this:
$ ebuild /usr/portage/pkg-categoty/some-package/some-package-1.0 unpack
$ cd /var/tmp/portage/pkg-categoty/some-package/work/...
$ patch -p1 < ~/my-patch-for-some-package
$ cd
$ ebuild /usr/portage/pkg-categoty/some-package/some-package-1.0 merge

It is lot of manual work. The idea is having an file, for example
/etc/portage/package.patch with contents like this:
=pkg-category/some-package-1*      /path/to/my-patch-for-some-package

Of course, patches could fail in newer versions. But when I'll use that
feature - I'll understand why it can be and it'll be more convenient to
maintain it.

-- 
gentoo-dev@gentoo.org mailing list



             reply	other threads:[~2006-12-21 14:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-21 14:32 Alexander Zubkov [this message]
2006-12-21 14:41 ` [gentoo-dev] portage idea - auto embed user patches Yuri Vasilevski
2006-12-21 15:12   ` Alexander Zubkov
2006-12-21 15:30     ` Alec Warner
2006-12-22  2:34       ` [gentoo-dev] " Steve Long
2006-12-22  3:47         ` Steev Klimaszewski
2006-12-23 18:18           ` Edward Catmur
2006-12-27 21:13             ` [gentoo-dev] " Steve Long
2006-12-21 14:50 ` [gentoo-dev] " Raymond Lewis Rebbeck
2006-12-21 15:03   ` Alexander Zubkov
2006-12-21 14:58 ` Timothy Redaelli
2006-12-21 16:01   ` Alexander Zubkov
2006-12-21 18:59 ` Bo Ørsted Andresen

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=458A9B09.7070804@area-b.msu.ru \
    --to=green@area-b.msu.ru \
    --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