Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 29213 - check CFLAGS and USE combatibility when emerging binary packages
Summary: check CFLAGS and USE combatibility when emerging binary packages
Status: RESOLVED WORKSFORME
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Enhancement/Feature Requests (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
: 34064 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-09-20 12:48 UTC by Benjamin Schulz
Modified: 2011-10-30 22:35 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin Schulz 2003-09-20 12:48:36 UTC
I want portage to emerge complete directorys.
Suppose on Computer A, I've emerged all packages with -b.

Now I copy that directory on a CD-rom and want my Laptop B to have the same
Software.

It would be goot If I coult type: 

emerge /mnt/cdrom/package-dir/
for packages or 
emerge /mnt/cdrom/source-archive-dir 
for source archives.

and then portage would analyze the depencies and what to emerge first and if
emerge is possible and try to emerge most of the packages.

This would improve network installation of gentoo.
Comment 1 Benjamin Schulz 2003-09-20 12:52:40 UTC
for this functionality, it would also be glad if portage would have a processor, and useflag-checking. It would cost a little to store the processor and the useflags the package was compiled with in the bz2 file and check them before emerge, just to assure that Packages that run only on a P4 dont get installed on a 386 for example
Comment 2 SpanKY gentoo-dev 2003-09-20 20:44:21 UTC
umm, you could simply do:
cd /mnt/cdrom/package-dir/
emerge *
Comment 3 Benjamin Schulz 2003-09-20 22:47:26 UTC
OK. Then i consider this bug as resolved.

Only this item with the processor flags would be interesting.
Comment 4 SpanKY gentoo-dev 2003-09-20 23:15:47 UTC
portage does store CFLAGS and USE settings in the binary packages it makes ...

i can see where you're going with the CFLAGS thing ... that would take some parsing on the portage side of things ... but i'm not so sure about the USE check you'd like to see
Comment 5 Benjamin Schulz 2003-09-20 23:35:35 UTC
with the useflags:

portage can shorly check the useflags. A package compiled with scanner installing where no scanner is available (-scanner useflag)

makes no sense.

(In my opinion it would also be good if I have an option io portage which can detect what packages must be recompiled when a Useflag is changed. That means: when I set scanner, and run portage with an option it tells me that kde-graphics must be recompiled. Portage puts a "Sucsess" file with no content at the end, when it is compiling. There it could also store the use parameters and cflags it has compiled the package with. When it compresses this information to bz2, not sufficient space will be lost)

Such a mechanism could also be used when checking binary packages
Comment 6 Marius Mauch (RETIRED) gentoo-dev 2003-11-21 15:41:46 UTC
*** Bug 34064 has been marked as a duplicate of this bug. ***
Comment 7 Nicholas Jones (RETIRED) gentoo-dev 2003-12-24 12:43:53 UTC
Rebuild on use change is a feature to be implemented with the
dep rewrite.

Closing this -- too much extraneous info in this bug.