From: James Dio <jim-list@psunit.com>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] post-LWE 2005
Date: Mon, 21 Feb 2005 09:23:47 -0500 [thread overview]
Message-ID: <1108995827.28494.33.camel@jimboy> (raw)
In-Reply-To: <20050221001427.GK25041@time.flatmonk.org>
[-- Attachment #1: Type: text/plain, Size: 1744 bytes --]
I had a great time at this, i'm no gentoo dev but from the pictures the
gentoo-meet-and-greet seemed to do well, too bad i couldnt have been
there. I only went up the first day of the expo and i guess things got
much better the later days.
On Sun, 2005-02-20 at 19:14 -0500, Aron Griffis wrote:
> Brian Harring wrote: [Sun Feb 20 2005, 05:33:40PM EST]
> > Err... enforcement in terms of forcing devs to sign everything?
> > That is only part of the pie. Take a _hard_ look at eclasses.
> > Then, take an even _harder_ look at profile bashrc's, and what they
> > technically are capable of, and the fact that all installations use
> > a profile (atm, there isn't a common profile that all inherit from,
> > but at some point it may occur).
>
> Oh yeah. I, um, forgot all that ;-)
>
> > So yeah. Assuming glep33 is greenlighted (a touch up will be posted
> > in the next few days of it), eclass/elib signing I'll be handling.
> > Profile signing is another beast that's needed, and help would be
> > appreciated (as always, clean patches/discussion of how to do it
> > properly/etc is always welcome).
> >
> > Beyond that, to save the portage devs sanity from people screaming
> > "SHA1 is broken!" (it's not, just weakened), I'll be looking at
> > centralizing, and making the digest code a bit more pluggable-
> > basically do a handler setup, mapping a CHF to a function...
>
> Cool, thanks for the reminder/update on these issues. Regarding
> profile signing... how about putting a (signed) manifest in each
> directory under portage/profiles? Only stuff in the immediate
> directory would be included, not the subdirs.
>
> Regards,
> Aron
>
> --
> Aron Griffis
> Gentoo Linux Developer
>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
parent reply other threads:[~2005-02-21 14:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20050221001427.GK25041@time.flatmonk.org>]
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=1108995827.28494.33.camel@jimboy \
--to=jim-list@psunit.com \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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