FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo Development

 
 
LinkBack Thread Tools
 
Old 09-25-2012, 06:03 PM
Ian Stakenvicius
 
Default Addressing GLEP-62 itself

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Since hasufell brought it up, and as I believe he's going to ask Council
to approve it before moving forward with this proposal towards including
it in an EAPI, I wanted to clarify some of the points mentioned:

- --- Quote, GLEP-62 ---
> Specifications, paragraph 3: The package manager should treat flags
> listed in IUSE_RUNTIME as regular USE flags, except for the
> following:
>
> 1. enabling or disabling any of the flags must not involve
> rebuilding the package,
>
> 2. it should be possible for a package manager to change those
> flags on a installed package without using the original ebuild,
>
> 3. when queried on a installed package, the package manager must
> consider a particular flag enabled only if its dependencies are
> satisfied already,
>
> 4. the flags may be listed in the visual output in a distinct way
> to inform the user that they affect runtime dependencies only.


#2 -- this would, if I'm understanding it properly, mean that the IUSE
list and the IUSE_RUNTIME list in the 'original ebuild' (ie in vdb)
would be ignored on an emerged package in favour of the ebuild(s) in
the tree, right? I'm not so sure this is a good idea.

IE, if IUSE and IUSE_RUNTIME have changed in the in-tree ebuild and
one of those use flags that changed have been triggered or
de-triggered I expect that the package should be rebuilt, to keep it
consistent with current practices.

IE2, shouldn't the original ebuild be what's used to trigger the
skip-rebuild functionality, rather than the in-tree ebuild?


#3 -- this seems to imply to me, that the state of a package's
effective USE could be modified solely on the basis of a dependency
existing or not and have nothing to do with what the flag was set to
at emerge time. IE, *not* the state of USE in the vdb. I think this
would also be a problem.

In order to properly handle dependency resolution (which IMO we should
do, because these are still USE flags) I think all use flag settings
should still be honoured by the PM and related metadata in the vdb be
updated for IUSE_RUNTIME flags identically to how it would be done if
IUSE_RUNTIME wasn't set.


Thoughts?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iF4EAREIAAYFAlBh8fgACgkQ2ugaI38ACPAENwD/VUmHAIQxuMF8p6FHYLtPk7J+
Xmar9LA0pNPTme27BiEA/3mKSC4VVlUMAT8IWxBcGCFcIQAx8pfirqhx7tfc3TZl
=4oUH
-----END PGP SIGNATURE-----
 

Thread Tools




All times are GMT. The time now is 06:00 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org