[gentoo-portage-dev] Thinking out loud

[gentoo-portage-dev] Thinking out loud

[Lisa Seelye]

[-- Attachment #1: Type: text/plain, Size: 1308 bytes --]

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.

Take, for instance, when OpenSSL is updated:  A lot of things need to be
recompiled to account for the library change, and merging openssl before
those other packages have been updated may cause problems.

So I was thinking (out loud) that if there was a facility to rebuild all
of the things that depend on openssl after a new openssl has been
compiled, perhaps still in the same sandbox, then we may eliminate some
need for revdep-rebuild.

Perhaps this could be handled with something similar to FEATURES. 
Perhaps a 'rebuild' flag that would traverse dependencies and rebuild
the packages with the new openssl libraries.

I think a problem might be distinguishing the old libraries from the
new.  To get around this, I think building a small chroot (Maybe just
mounting other things, such as /bin, /usr/bin, /sbin, /dev or /sys as
read-only) to compile in may be needed.

Just thinking out loud, maybe this could be a mainstay of Portage-ng or
handled in some third party plug-in.


-- 
Regards,
-Lisa
<Vix ulla tam iniqua pax, quin bello vel aequissimo sit potior>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-portage-dev] Thinking out loud

[Philippe Lafoucrière]

> Take, for instance, when OpenSSL is updated:  A lot of things need to be
> recompiled to account for the library change, and merging openssl before
> those other packages have been updated may cause problems.
>
> So I was thinking (out loud) that if there was a facility to rebuild all
> of the things that depend on openssl after a new openssl has been
> compiled, perhaps still in the same sandbox, then we may eliminate some
> need for revdep-rebuild.


sounds good [+1]


--
gentoo-portage-dev@gentoo.org mailing list

Re: [gentoo-portage-dev] Thinking out loud

[Daniel Robbins]

[-- Attachment #1: Type: text/plain, Size: 344 bytes --]

On Mon, 2003-12-08 at 09:33, Lisa Seelye wrote:
> So I was thinking (out loud) that if there was a facility to rebuild all
> of the things that depend on openssl after a new openssl has been
> compiled, perhaps still in the same sandbox, then we may eliminate some
> need for revdep-rebuild.

This is a great idea.

Regards,

Daniel

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-portage-dev] Thinking out loud

[Joel Konkle-Parker]

Quoting Daniel Robbins <drobbins@gentoo.org>:

> On Mon, 2003-12-08 at 09:33, Lisa Seelye wrote:
> > So I was thinking (out loud) that if there was a facility to rebuild
> all
> > of the things that depend on openssl after a new openssl has been
> > compiled, perhaps still in the same sandbox, then we may eliminate
> some
> > need for revdep-rebuild.

yes [+1]


-- 
Joel Konkle-Parker
Webmaster [Ballsome.com]

Phone     [662-518-1636]
E-mail    [jjk3@msstate.edu]

--
gentoo-portage-dev@gentoo.org mailing list

Re: [gentoo-portage-dev] Thinking out loud

[Yannick Le Saint (kyncani)]

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

Re: [gentoo-portage-dev] Thinking out loud

[Lisa Seelye]

[-- Attachment #1: Type: text/plain, Size: 916 bytes --]

On Mon, 2003-12-08 at 11:33, Lisa Seelye wrote:
> So I was thinking (out loud) that if there was a facility to rebuild all
> of the things that depend on openssl after a new openssl has been
> compiled, perhaps still in the same sandbox, then we may eliminate some
> need for revdep-rebuild.


Something else hit me while I was recompiling modules (i have a shell
script to automate it) for a new kernel.

Why not some functionality to rebuild kernel modules.  Perhaps, using
today's terminology:

Alsa, lm_sensors, Nvidia-kernel, Nvidia-glx, and others will have a
line:

provides kernel-module

You can issue the command:

emerge --rebuildmodules

or something like that after rebooting and Portage will resolve all
sorts of fun stuff and then insert these new modules into the
/lib/modules place.


-- 
Regards,
-Lisa
<Vix ulla tam iniqua pax, quin bello vel aequissimo sit potior>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]