From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [RFC] Add 'emerge --sync-glsa' action and 'emaint sync-glsa' command
Date: Wed, 17 Dec 2014 15:03:59 -0800 [thread overview]
Message-ID: <20141217150359.695f3e73.dolsen@gentoo.org> (raw)
In-Reply-To: <54920894.6090106@gentoo.org>
On Wed, 17 Dec 2014 17:49:56 -0500
Michael Orlitzky <mjo@gentoo.org> wrote:
> On 12/17/2014 05:32 PM, Brian Dolbec wrote:
> >
> > Only code changes I see to portage, pkgcore (I know nothing about
> > paludis) are to look for the glsa's in the 2 possible locations.
> > The standalone glsa repo, failing that, backup to the gentoo tree.
> >
>
> Could we ship a GLSA overlay enabled by default, regardless of what we
> do with the main repo? Then for simplicity, we update the tools to
> check metadata/glsa in overlays as well. No need to special-case a
> fallback location.
>
> glsa-check would of course want to sync the GLSA repo before running.
>
>
yes, that is a very simple edit to the default repos.conf file adding
the glsa repo. Yes, I forgot that glsa-check needed changes
so it would/could be configured to sync the repo too.
Pkgcore does not have the capability (yet) to read/use extended
repos.conf repo attributes. So, would need more code changes. I think
pkgcore does not yet handle repos.conf files... I'm not sure.
--
Brian Dolbec <dolsen>
next prev parent reply other threads:[~2014-12-17 23:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 20:30 [gentoo-portage-dev] [RFC] Add 'emerge --sync-glsa' action and 'emaint sync-glsa' command Zac Medico
2014-12-17 22:32 ` Brian Dolbec
2014-12-17 22:49 ` Michael Orlitzky
2014-12-17 23:03 ` Brian Dolbec [this message]
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=20141217150359.695f3e73.dolsen@gentoo.org \
--to=dolsen@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