From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:plugin-sync commit in: pym/_emerge/
Date: Mon, 1 Dec 2014 21:50:05 +0000 (UTC) [thread overview]
Message-ID: <1417470580.e757fbbee36c06c537edf1f6581190a2ce81a31c.mgorny@gentoo> (raw)
commit: e757fbbee36c06c537edf1f6581190a2ce81a31c
Author: Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Sun May 11 17:05:17 2014 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Mon Dec 1 21:49:40 2014 +0000
URL: http://sources.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=e757fbbe
_emerge/main.py: Set portage._sync_mode for --sync
This allows repos with non-existent directories to be available.
If the new repo is set for auto-sync, then it can be created with the sync module's new().
---
pym/_emerge/main.py | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/pym/_emerge/main.py b/pym/_emerge/main.py
index 85cdc24..1506207 100644
--- a/pym/_emerge/main.py
+++ b/pym/_emerge/main.py
@@ -1057,6 +1057,10 @@ def emerge_main(args=None):
elif myaction == "moo":
print(COWSAY_MOO % platform.system())
return os.EX_OK
+ elif myaction == "sync":
+ # need to set this to True now in order for the repository config
+ # loading to allow new repos with non-existent directories
+ portage._sync_mode = True
# Portage needs to ensure a sane umask for the files it creates.
os.umask(0o22)
next reply other threads:[~2014-12-01 21:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 21:50 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-21 5:05 [gentoo-commits] proj/portage:plugin-sync commit in: pym/_emerge/ Zac Medico
2014-10-21 5:05 Zac Medico
2014-10-20 3:54 Zac Medico
2014-10-20 3:54 Zac Medico
2014-10-20 3:54 Zac Medico
2014-09-30 0:46 Brian Dolbec
2014-09-30 0:46 Brian Dolbec
2014-09-30 0:46 Brian Dolbec
2014-09-29 18:29 Brian Dolbec
2014-09-29 18:29 Brian Dolbec
2014-09-27 2:20 Brian Dolbec
2014-09-27 2:20 Brian Dolbec
2014-09-05 21:15 Brian Dolbec
2014-09-05 21:15 Brian Dolbec
2014-09-05 21:15 Brian Dolbec
2014-09-05 4:38 Brian Dolbec
2014-09-04 1:18 Brian Dolbec
2014-09-03 23:36 Brian Dolbec
2014-09-03 23:36 Brian Dolbec
2014-09-03 23:36 Brian Dolbec
2014-06-16 22:45 Brian Dolbec
2014-06-16 22:45 Brian Dolbec
2014-06-16 22:45 Brian Dolbec
2014-06-16 15:46 Brian Dolbec
2014-06-16 15:46 Brian Dolbec
2014-06-16 15:46 Brian Dolbec
2014-06-16 15:18 Brian Dolbec
2014-06-16 15:18 Brian Dolbec
2014-06-16 15:18 Brian Dolbec
2014-05-11 17:22 Brian Dolbec
2014-05-02 23:13 Brian Dolbec
2014-05-02 23:13 Brian Dolbec
2014-04-22 2:36 Brian Dolbec
2014-04-22 2:36 Brian Dolbec
2014-01-29 4:10 Brian Dolbec
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=1417470580.e757fbbee36c06c537edf1f6581190a2ce81a31c.mgorny@gentoo \
--to=mgorny@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