From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] [RFC] Add 'emerge --sync-glsa' action and 'emaint sync-glsa' command
Date: Wed, 17 Dec 2014 12:30:53 -0800 [thread overview]
Message-ID: <5491E7FD.2080203@gentoo.org> (raw)
Hi,
For server deployments, it's common for administrators to want to use
glsa-check for security vulnerabilities, without necessarily wanting to
to do a full sync [1].
So, I propose that we add an 'emerge --sync-glsa' action and a
corresponding 'emaint sync-glsa' command that will only sync the
relevant metadata/glsa subdirectory of the relevant repository(s).
Please respond if you agree or disagree with this proposal.
[1] https://bugs.gentoo.org/show_bug.cgi?id=89641
--
Thanks,
Zac
next reply other threads:[~2014-12-17 20:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 20:30 Zac Medico [this message]
2014-12-17 22:32 ` [gentoo-portage-dev] [RFC] Add 'emerge --sync-glsa' action and 'emaint sync-glsa' command Brian Dolbec
2014-12-17 22:49 ` Michael Orlitzky
2014-12-17 23:03 ` Brian Dolbec
2014-12-17 23:57 ` Zac Medico
2014-12-18 2:20 ` Zac Medico
2014-12-19 1:07 ` Zac Medico
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=5491E7FD.2080203@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-portage-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