| 1 |
On Mon, Mar 30, 2015 at 6:02 AM, Stefan G. Weichinger <lists@×××××.at> wrote: |
| 2 |
> |
| 3 |
> OK, then so why do I have to edit files to tell the system to USE this |
| 4 |
> and that after the system tells me it needs that ... ? |
| 5 |
> |
| 6 |
> Why isn't this taken care of within portage itself? |
| 7 |
> |
| 8 |
> I don't *want* to decide 32bit or not ... (I like that I *can* ...) |
| 9 |
> |
| 10 |
|
| 11 |
This goes way beyond 32-bit. |
| 12 |
|
| 13 |
The way things work in Gentoo right now is that portage can decide to |
| 14 |
install a package at any time without any config file changes (unless |
| 15 |
it is keyword/package masked). However, it can't change the USE |
| 16 |
configuration of a package unless this ends up in a config file. |
| 17 |
|
| 18 |
In a sense I think giving portage more freedom to do this would be |
| 19 |
better. It does increase the likelihood of blockers, but we already |
| 20 |
deal with those for package blocks. It would also mean that a proper |
| 21 |
depclean might actually involve package rebuilds (unless we make |
| 22 |
depclean just remove stuff, and an emerge -N rebuild stuff). |
| 23 |
|
| 24 |
I'm trying to think of what the downside is to just letting portage |
| 25 |
set the flags however seems best unless a flag is explicitly set or |
| 26 |
unset in configuration. I can't think of any issues offhand - I think |
| 27 |
that most of the work that needs to be done by emerge to calculate |
| 28 |
deps needs to be done anyway. Obviously it would take effort to do. |
| 29 |
|
| 30 |
I ended up with 800 lines being added to my package.use, which now |
| 31 |
constitutes 2/3rds of the file. Granted, most of those are comments. |
| 32 |
|
| 33 |
Some of the comments are also less than ideal, like: |
| 34 |
# required by media-libs/libgphoto2-2.5.7 |
| 35 |
# required by kde-base/kamera-4.14.3 |
| 36 |
# required by kde-base/kdegraphics-meta-4.14.3 |
| 37 |
# required by kde-base/kde-meta-4.14.3 |
| 38 |
# required by @selected |
| 39 |
# required by @world (argument) |
| 40 |
>=virtual/libusb-1-r1 abi_x86_32 |
| 41 |
|
| 42 |
This tends to imply that kde-meta needs 32-bit libusb. I suspect that |
| 43 |
some other package does need 32-bit libgphoto2, which then needs |
| 44 |
32-bit libusb, but kde-meta shows up in the comment instead. |
| 45 |
|
| 46 |
The packages that gave me the most trouble were wine and steam. I |
| 47 |
don't think there were any problems with them - they just pull in a |
| 48 |
lot of 32-bit deps. |
| 49 |
|
| 50 |
-- |
| 51 |
Rich |
Archives