From: Luca Barbato <lu_zero@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Usage of cp -i to prevent overwriting upstream files
Date: Sat, 31 Jan 2009 09:13:58 +0100 [thread overview]
Message-ID: <49840846.7000102@gentoo.org> (raw)
In-Reply-To: <1232565775.7247.17.camel@mangurrian>
Santiago M. Mola wrote:
> e) use a hook around unpack on your local system to detect new build.xml
> for a list of packages.
>
> AFAIK, checking changes is part of the bump process, so I think that's a
> check you can do either at hand, with a script (it's always a good thing
> to look for new files in the project, or look at the diffs), or as I
> said in 'e)', use some tricks with /etc/portage/bashrc.
That looks interesting.
lu
--
Luca Barbato
Gentoo Council Member
Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero
prev parent reply other threads:[~2009-01-31 8:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 19:04 [gentoo-dev] Usage of cp -i to prevent overwriting upstream files Petteri Räty
2009-01-20 19:24 ` Ferris McCormick
2009-01-20 19:37 ` Petteri Räty
2009-01-20 20:18 ` Ferris McCormick
2009-01-20 22:50 ` Jan Kundrát
2009-01-20 23:40 ` Ferris McCormick
2009-01-20 23:57 ` Jeremy Olexa
2009-01-21 17:00 ` Peter Volkov
2009-01-21 19:22 ` Santiago M. Mola
2009-01-31 8:13 ` Luca Barbato [this message]
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=49840846.7000102@gentoo.org \
--to=lu_zero@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