Bug 27553

Summary:	Change to fixpackages
Product:	Portage Development	Reporter:	Benedict Verhegghe <benedict.verhegghe>
Component:	Enhancement/Feature Requests	Assignee:	Portage team <dev-portage>
Status:	RESOLVED WONTFIX
Severity:	enhancement	CC:	mr_bones_
Priority:	High
Version:	2.0
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Benedict Verhegghe 2003-08-29 11:38:00 UTC

I propose a change to the portage system, more notably the invoking of
fixpackages. It would be nice to have the possibility to not run fixpackages on
every emerge, but instead have a binary package fixed only if and when it is
actually  going to be emerged. 

For those that do not use binary packages, it would mean that they never use
fixpackages. For those that do, it would save a lot of processing time.
Such users tend to create binary packages by default, and lots of them get never
used.

Though I'm not too familiar with the internals of portage, I guess that it
should not be too difficult to implement. Fixpackages would have to be run only
on an emerge -k, and only on the packages to be extracted.
Also, it should not be invoked when the -p switch is added.



Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1 Axxackall 2003-08-29 15:12:32 UTC

I support this idea. Consider my vote for it.

Comment 2 Nicholas Jones (RETIRED) gentoo-dev

2003-08-31 13:30:25 UTC

That doesn't work. Portage cannot take care of packages at that level.

fixpackages corrects all the metadata within a tbz2 to ensure that it
is valid for the current portage tree. It's not much help if it is
randomly out of date.

Determining exactly where a package has become out of date is well
beyond trivial and it's a bit too complicated internally to warrant
dealing with it that way.