From: Taahir Ahmed <ahmed.taahir@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Cleaning up integration of external repos into ::gentoo
Date: Sun, 16 Aug 2015 19:38:39 -0500 [thread overview]
Message-ID: <3335087.dWjSifASTH@basis> (raw)
In-Reply-To: <CAGfcS_ncUTA=n0Wz0jebCBEDUCjf2iJQVaS-BbcB-575dOAkUw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]
On Thu, Aug 13, 2015 at 5:26 AM, Andrew Savchenko <bircoph@gentoo.org> wrote:
> IMO the best way will be to put mandatory stuff in the
> repo/gentoo.git.
On Thursday 13 August 2015 07:02:59 Rich Freeman wrote:
> Tend to agree. The main reason not to would be if they were
> maintained by different groups and we wanted to control access. If
> "news" were about PR that might be a real issue, but the GLEP news is
> more about package notifications, and the security team probably also
> needs tree access as well, so at least at present I'm not sure I see
> the need to separate them. GLSA state is also pretty closely
> associated with tree state so it really seems like it should be in the
> tree.
Is there some consensus on integrating this stuff into the main
repository?
I've recently converted my cave setup to directly sync from the git
mirror. Hasufell wrote an excellent example configuration for cave [1],
but 90% of the configuration changes are hooks for gluing clones of dtd,
glsa, herds, and news into the checked-out copy of repos/gentoo.git.
Things would be a lot simpler if these were just in repos/gentoo.git,
especially since they are tightly coupled to the state of the tree.
[1] https://github.com/hasufell/paludis-gentoo-git-config/tree/master/etc/paludis/hooks/sync_all_post
Taahir Ahmed
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-08-17 0:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 7:12 [gentoo-dev] Cleaning up integration of external repos into ::gentoo Michał Górny
2015-08-13 9:26 ` Andrew Savchenko
2015-08-13 11:02 ` Rich Freeman
2015-08-17 0:38 ` Taahir Ahmed [this message]
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=3335087.dWjSifASTH@basis \
--to=ahmed.taahir@gmail.com \
--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