-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 06 November 2003 11:38, Klavs Klavsen wrote: > > And besides the ebuild maintainer shouldn't have to maintain such a > general thing - could be done using standard scripts. > ie. IMHO we need a generic solution for this problem, so every ebuild > maintainer doesn't have to implement his solution for the problem. > > What do you guys think of the proposed implementation? > > I will gladly implement shell-scritps (I don't know python) that do > what the GLEP proposes, as a v0.1 system, which portage could call > upon. >
There are basically only two ways to do rebuilding when necessary: - - use a revdep like approach. This does not work perfectly and is a big resource drain as all libraries and binaries need to be checked for a dependency on the lib. Further this does not work for on-demand loaded libraries so is only a partial "solution". It is basically a shotgun solution that still manages to miss things. - - Devise a way that emerge knows (either automatically or specified) that the libraries in a package have changed and rebuild all packages that depend on the package. Finding out the change automatically should not be too complicated. However finding out which packages need to be rebuild is. Especially since dependencies can be indirect. This approach is a lot cleaner although even here there can be no guarantee of correctness. I like the second way. However it requires significant changes to portage so is unlikely to happen soon. Paul - -- Paul de Vrieze Gentoo Developer Mail: [EMAIL PROTECTED] Homepage: http://www.devrieze.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/qik+bKx5DBjWFdsRAkcvAJ4yLDxeBrShCL71PPPAiUE9oW9gYwCfXSvA AEn1Y9ApcssLG1I14uXaE1M= =OPu2 -----END PGP SIGNATURE----- -- [EMAIL PROTECTED] mailing list
