From: "Yannick Le Saint (kyncani)" <y.lesaint@free.fr>
To: gentoo-portage-dev@gentoo.org
Subject: Re: [gentoo-portage-dev] Thinking out loud
Date: Mon, 08 Dec 2003 18:15:08 +0000 [thread overview]
Message-ID: <1070907305.1241.86.camel@kyncani.lesaint> (raw)
In-Reply-To: <1070901222.14948.1408.camel@lisa.thedoh.com>
On Mon, 2003-12-08 at 16:33, Lisa Seelye wrote:
> I'm just thinking out loud here, so bear with me.
>
> I was thinking that when compiling packages it may be desirable to not
> merge each package [outside of the sandbox] until some other steps have
> been done.
Sound good for me too :) [+1]
But what should be done if openssl has to be upgraded according to a
GLSA, and some of its revdep dependencies cannot be merged for some
reason ?
Would openssl be merged anyway (thus breaking some packages), or would
a non-secure openssl library stay current ?
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-12-08 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 16:33 [gentoo-portage-dev] Thinking out loud Lisa Seelye
2003-12-08 16:52 ` Philippe Lafoucrière
2003-12-08 16:59 ` Daniel Robbins
2003-12-08 16:59 ` Joel Konkle-Parker
2003-12-08 18:15 ` Yannick Le Saint (kyncani) [this message]
2003-12-11 19:07 ` Lisa Seelye
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=1070907305.1241.86.camel@kyncani.lesaint \
--to=y.lesaint@free.fr \
--cc=gentoo-portage-dev@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