From: Max Kalika <max+lists.gentoo-dev@lsit.ucsb.edu>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] RFC for a small change to echangelog
Date: Thu, 12 Jun 2003 13:45:05 -0700 [thread overview]
Message-ID: <113160000.1055450705@valkyrie.lsit.ucsb.edu> (raw)
Greetings. What do you all think of this small fix for echangelog? This
way it can work in PORTDIR_OVERLAY without having to copy skel.ChangeLog to
the appropriate place (../../).
--- echangelog.orig 2003-06-12 06:27:08.000000000 -0700
+++ echangelog 2003-06-12 06:37:48.000000000 -0700
@@ -30,8 +30,10 @@
} else {
# No ChangeLog here, maybe we should make one...
if (<*.ebuild>) {
- open I, '<../../skel.ChangeLog'
- or die "Can't open ../../skel.ChangeLog for input: $!\n";
+ my ($portdir) = `/usr/bin/portageq portdir 2>/dev/null`;
+ chomp($portdir);
+ open I, "<$portdir/skel.ChangeLog"
+ or die "Can't open $portdir/skel.ChangeLog for input: $!\n";
{ local $/ = undef; $text = <I>; }
close I;
my ($cwd) = getcwd();
---max kalika
--max@lsit.ucsb.edu
-lsit systems administrator
--
gentoo-dev@gentoo.org mailing list
reply other threads:[~2003-06-12 20:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=113160000.1055450705@valkyrie.lsit.ucsb.edu \
--to=max+lists.gentoo-dev@lsit.ucsb.edu \
--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