From: Georgi Georgiev <chutz@gg3.net>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] portage and "Global Updates"
Date: Fri, 19 Sep 2003 13:15:12 +0900 [thread overview]
Message-ID: <20030919041511.GA7920%chutz@gg3.net> (raw)
I have a question about the "Global Updates" that portage currently performs
every now and then (moving packages and stuff...).
I am not clear how exactly it works, but is there a reason why the files are
named #Q-YEAR? Since portage applies the updates in alphabetic order and since
interrupting portage at inappropriate time makes it try and perform the updates
in all files, doesn't it make more sense to name the files so that they sort in
time ascending order? Instead of 3Q-2003 make it 2003-3Q.
--
\ Georgi Georgiev \ Horse sense is the thing a horse has which \
/ chutz@gg3.net / keeps it from betting on people. -- W. C. /
\ +81(90)6266-1163 \ Fields \
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2003-09-19 4:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-19 4:15 Georgi Georgiev [this message]
2003-09-19 5:19 ` [gentoo-dev] portage and "Global Updates" Marius Mauch
2003-09-20 18:41 ` Martin Schlemmer
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=20030919041511.GA7920%chutz@gg3.net \
--to=chutz@gg3.net \
--cc=chutz-dated-1065154514.3793ede2cb08@gg3.net \
--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