From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/grss:master commit in: /
Date: Tue, 4 Aug 2015 19:25:10 +0000 (UTC) [thread overview]
Message-ID: <1438716490.9b7f11ebb6ea1fcdf459641ddfe3d66b793c516f.blueness@gentoo> (raw)
commit: 9b7f11ebb6ea1fcdf459641ddfe3d66b793c516f
Author: Anthony G. Basile <blueness <AT> gentoo <DOT> org>
AuthorDate: Tue Aug 4 19:28:10 2015 +0000
Commit: Anthony G. Basile <blueness <AT> gentoo <DOT> org>
CommitDate: Tue Aug 4 19:28:10 2015 +0000
URL: https://gitweb.gentoo.org/proj/grss.git/commit/?id=9b7f11eb
TODO: note problem with orphaned files in /etc/portage.
TODO | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/TODO b/TODO
index db32c13..ed1164c 100644
--- a/TODO
+++ b/TODO
@@ -6,3 +6,9 @@ to prevent wierdness in case /usr/portage changes during a run.
2. Upon building a system we should make use of the binpkgs in CONST.TMPDIR + GRS name
as a time saver. This is something to go into the build scripts in the GRS repo and not
in the GRS suite.
+
+3. grsup and clean-worldconf should remove files form /etc/portage that correspond to
+sections that were removed from world.conf since the last time grsup or install-worldconf
+was run. Currently, if a section is removed from world.conf on the remote repo, then any
+files in canonical form in /etc/portage are orphaned. This can lead to trouble because
+the the flags they define are not removed. This needs to be fixed in clean() in grs/WorldConf.py.
next reply other threads:[~2015-08-04 19:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 19:25 Anthony G. Basile [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-02 22:06 [gentoo-commits] proj/grss:master commit in: / Anthony G. Basile
2015-08-08 20:26 Anthony G. Basile
2015-08-08 17:52 Anthony G. Basile
2015-08-04 21:41 Anthony G. Basile
2015-08-04 19:32 Anthony G. Basile
2015-07-25 22:06 Anthony G. Basile
2015-07-25 15:32 Anthony G. Basile
2015-07-25 1:51 Anthony G. Basile
2015-07-25 1:24 Anthony G. Basile
2015-07-10 21:13 Anthony G. Basile
2015-07-07 12:38 Anthony G. Basile
2015-07-07 0:41 Anthony G. Basile
2015-07-06 19:57 Anthony G. Basile
2015-07-06 19:49 Anthony G. Basile
2015-07-06 1:39 Anthony G. Basile
2015-07-05 23:56 Anthony G. Basile
2015-07-05 16:33 Anthony G. Basile
2015-07-05 16:20 Anthony G. Basile
2015-07-05 16:11 Anthony G. Basile
2015-07-05 15:19 Anthony G. Basile
2015-07-05 12:40 Anthony G. Basile
2015-07-04 14:13 Anthony G. Basile
2015-07-02 16:51 Anthony G. Basile
2015-07-01 18:12 Anthony G. Basile
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=1438716490.9b7f11ebb6ea1fcdf459641ddfe3d66b793c516f.blueness@gentoo \
--to=blueness@gentoo.org \
--cc=gentoo-commits@lists.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