Re: [gentoo-user] dev-libs/efl-1.8.0_beta2 fails to emerge on x86
On Saturday 07 Dec 2013 10:51:55 you wrote: On Sat, 7 Dec 2013 10:48:21 + Mick michaelkintz...@gmail.com wrote: lib/edje/.libs/libedje.so: undefined reference to `eet_mmap' This sounds like a bug to me, can you file a bug at https://bugs.gentoo.org and attach the complete build log as well as comment with the output of `emerge --info`? Thank you in advance. Here you are: https://bugs.gentoo.org/show_bug.cgi?id=493536 I'm holding on for trying it on amd64 (my main box) because last time I attempted to move to enlightenment-1.8 from 1.7.5 I came up across a number of blockers and some confusion on the appropriate steps. I didn't have time to look into it but it seemed to me at the time that it would be more of a 'migration' than a simple update. If this is so are there any gentoo-centric instructions to achieve this? Thanks again for your help. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] is there a good independent power-manager?
On Sat, Dec 07, 2013 at 08:19:14PM +0100, Benjamin Block wrote The thing is, on my laptop I used to use the gnome-power-manager along with cpufreqd and laptop-mode to manage battery-mode. Is there any good replacement for this tool that doesn't belong to one of the big desktop-environments (I use i3 since 2 years ago)? I use sys-power/cpufrequtils which is a commandline tool. It installs cpufreq-info and cpufreq-set. E.g. the command... cpufreq-set -r -g conservative will select the conservative power-governor. The -r tells it to set all cores (which I assume you want). If you want to get fancy, you can tweak acpid to call cpufreq-set when certain events happen; e.g. the screen is folded down, AC power is (dis)connected, etc. -- Walter Dnes waltd...@waltdnes.org I don't run desktop environments; I run useful applications
[gentoo-user] NetworkManager stays in inactive mode
Hi, I updated this week and since then I have problem with NetworkManager. It starts, but last message is WARNING: NetworkManager has started, but is inactive and the network is not set up :-( networkmanager-0.9.8.8 nm-applet-0.9.8.8 kernel 3.10.17-gentoo Please, point me to the solution. Thanks Pat Freehosting PIPNI - http://www.pipni.cz/
Re: [gentoo-user] NetworkManager stays in inactive mode
On Sun, Dec 8, 2013 at 7:00 AM, p...@xvalheru.org wrote: Hi, I updated this week and since then I have problem with NetworkManager. It starts, but last message is WARNING: NetworkManager has started, but is inactive and the network is not set up :-( networkmanager-0.9.8.8 nm-applet-0.9.8.8 kernel 3.10.17-gentoo Please, point me to the solution. Thanks Pat Hi Pat, Here is what I did, look at the post by comprookie2000; https://forums.gentoo.org/viewtopic-t-973974-highlight-.html
[gentoo-user] Re: [systemd] lvm.service running too early? [HACKED]
On 12/07/2013 05:58 PM, gottl...@nyu.edu wrote: On Sat, Dec 07 2013, Canek Peláez Valdés wrote: On Dec 7, 2013 12:40 PM, walt w41...@gmail.com wrote: Just updated my stable amd64 machine to use systemd and all is working okay except for the lvm.service. The lvm.service starts with no errors, but OTOH it finds no physical or logical volumes. I suspect this happens because the drive using lvm2 is in a usb3 external dock instead of attached to the mobo. When I run 'systemctl restart lvm' manually, the usb3 disk is activated and mounted successfully. Thus I think the lvm.service runs too early during boot. Here is my lvm.service (which I copied from another distro, IIRC): #cat /etc/systemd/system/lvm.service [Unit] Description=LVM DefaultDependencies=no Requires=systemd-udev-settle.service Before=shutdown.target local-fs.target [Service] Type=oneshot RemainAfterExit=yes ExecStart=/sbin/pvscan --ignorelockingfailure ExecStart=/sbin/vgscan --mknodes --ignorelockingfailure ExecStart=/sbin/vgchange --sysinit -a ly ExecStop=/sbin/lvchange --sysinit -a ln $(/sbin/vgs -o vg_name --noheadings --nosuffix) ExecStop=/sbin/lvchange --sysinit -a ln ExecStop=/sbin/vgchange --sysinit -a ln [Install] WantedBy=sysinit.target Is there an elegant way to fix the problem as opposed to a hack? I believe that for recent enough versions of LVM2, it includes an official lvm2.service unit file(s). Could you try that one and see if it works as you expect? It has the same problem. I looked more carefully at the systemd logs and found that lvm was running before the xhci kernel module was loaded, hence the usb3 drive was not visible yet. I fixed the problem by adding After=basic to the lvm.service file, and now it works as expected. (Expected by me, anyway :) I have the recent lvm2 (2.02.104) and the unit files in /usr/lib/systemd/system are called lvm2-lvmetad.service lvm2-lvmetad.socket lvm2-monitor.service lvm2-pvscan@.service That last file must have been added for version .104. I'll take a look, thanks.
Re: [gentoo-user] Re: [systemd] lvm.service running too early? [HACKED]
On Sun, Dec 8, 2013 at 10:15 AM, walt w41...@gmail.com wrote: On 12/07/2013 05:58 PM, gottl...@nyu.edu wrote: On Sat, Dec 07 2013, Canek Peláez Valdés wrote: On Dec 7, 2013 12:40 PM, walt w41...@gmail.com wrote: Just updated my stable amd64 machine to use systemd and all is working okay except for the lvm.service. The lvm.service starts with no errors, but OTOH it finds no physical or logical volumes. I suspect this happens because the drive using lvm2 is in a usb3 external dock instead of attached to the mobo. When I run 'systemctl restart lvm' manually, the usb3 disk is activated and mounted successfully. Thus I think the lvm.service runs too early during boot. Here is my lvm.service (which I copied from another distro, IIRC): #cat /etc/systemd/system/lvm.service [Unit] Description=LVM DefaultDependencies=no Requires=systemd-udev-settle.service Before=shutdown.target local-fs.target [Service] Type=oneshot RemainAfterExit=yes ExecStart=/sbin/pvscan --ignorelockingfailure ExecStart=/sbin/vgscan --mknodes --ignorelockingfailure ExecStart=/sbin/vgchange --sysinit -a ly ExecStop=/sbin/lvchange --sysinit -a ln $(/sbin/vgs -o vg_name --noheadings --nosuffix) ExecStop=/sbin/lvchange --sysinit -a ln ExecStop=/sbin/vgchange --sysinit -a ln [Install] WantedBy=sysinit.target Is there an elegant way to fix the problem as opposed to a hack? I believe that for recent enough versions of LVM2, it includes an official lvm2.service unit file(s). Could you try that one and see if it works as you expect? It has the same problem. I looked more carefully at the systemd logs and found that lvm was running before the xhci kernel module was loaded, hence the usb3 drive was not visible yet. I fixed the problem by adding After=basic to the lvm.service file, and now it works as expected. (Expected by me, anyway :) Well, at least is working, however is kinda an ugly fix. Could you create the file /etc/modules-load.d/usb3.conf, with the line xhci in it, reboot, and see if your little hack is not needed then? Also, if you are using an initramfs, could you rebuild it before trying? I have the recent lvm2 (2.02.104) and the unit files in /usr/lib/systemd/system are called lvm2-lvmetad.service lvm2-lvmetad.socket lvm2-monitor.service lvm2-pvscan@.service That last file must have been added for version .104. I'll take a look, thanks. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] Re: [systemd] lvm.service running too early? [HACKED]
On Sun, 8 Dec 2013 11:12:23 -0600, Canek Peláez Valdés wrote: It has the same problem. I looked more carefully at the systemd logs and found that lvm was running before the xhci kernel module was loaded, hence the usb3 drive was not visible yet. I fixed the problem by adding After=basic to the lvm.service file, and now it works as expected. (Expected by me, anyway :) Well, at least is working, however is kinda an ugly fix. Could you create the file /etc/modules-load.d/usb3.conf, with the line xhci in it, reboot, and see if your little hack is not needed then? Also, if you are using an initramfs, could you rebuild it before trying? Alternatively, build xhci into the kernel, since you need it at every boot. -- Neil Bothwick For security reasons, all text in this mail is double-rot13 encrypted. signature.asc Description: PGP signature
SOLVED - Re: [gentoo-user] Merging separate /usr back into / - one last time...
On 2013-12-03 8:19 AM, Tanstaafl tansta...@libertytrek.org wrote: Current command I'll be using: rsync -avHP --numeric-ids /mnt/gentoo/oldusr/ /mnt/gentoo/usr/ Well, that was about as uneventful as it gets... Took all of 6 minutes (and almost all of that was rsyncing /usr)... Made a forum post in case anyone else wants to do this and may be a little hesitant like I was... http://forums.gentoo.org/viewtopic-p-7457324.html#7457324 Thanks to all who patiently answered my questions... I now have /usr merged back into / and no longer have to choose between using an intramfs (which I vehemently did not want to do) and updating my system without fear of breakage. whew
[gentoo-user] Install software using ebuilds on other systems
Hi all, I have one question. There is a nice project called gentoo-prefix that allows to install Gentoo in other systems locally. It is really greate, but if one needs to easily install only a little number of packages it can be quite boring to compile the whole base system to be able to do so. Hence my question, is there a way to use portage to install software per user on a different system using its system compiler etc.? Without dependency checking of course ) I want just use an ebuild, so I do not need to configure, make and install stuff by hand. Thanks for answer, regards, Jauhien signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] NFS kernel bug
On 2013-10-26 6:19 PM, Daniel Frey djqf...@gmail.com wrote: Just a note to other NFS server users - There's a kernel bug that can cause unmounting an NFS share to segfault (and not actually unmount anything.) I had in in the kernel 3.10 version, perhaps even before that as I don't update the kernel on my mythtv backend server that often. It hangs the shutdown process with an oops and it will require physical manual intervention to shut the machine down. If you upgrade to 3.11.5 or greater the problem goes away. I've been banging my head against the wall with this for over a week and *finally* found a resolution after going through a lot of NFS searches via Google. So... is this fixed in the stable 3.10 series (ie, 3.10.7 or 3.10.17)?
Re: [gentoo-user] Install software using ebuilds on other systems
On 12/08/2013 04:11 PM, Jauhien Piatlicki wrote: Hi all, I have one question. There is a nice project called gentoo-prefix that allows to install Gentoo in other systems locally. It is really greate, but if one needs to easily install only a little number of packages it can be quite boring to compile the whole base system to be able to do so. Hence my question, is there a way to use portage to install software per user on a different system using its system compiler etc.? Without dependency checking of course ) I want just use an ebuild, so I do not need to configure, make and install stuff by hand. This isn't going to work for non-trivial packages, but, emerge --nodeps foo might fly if everything is present where the build system expects it to be. If I were you I would suck it up and build the whole @system, it will save time in the long run.
[gentoo-user] Re: [systemd] lvm.service running too early? [HACKED--]
On 12/08/2013 10:39 AM, Neil Bothwick wrote:
On Sun, 8 Dec 2013 11:12:23 -0600, Canek Peláez Valdés wrote:
It has the same problem. I looked more carefully at the systemd logs
and found that lvm was running before the xhci kernel module was
loaded, hence the usb3 drive was not visible yet.
I fixed the problem by adding After=basic to the lvm.service
file, and now it works as expected. (Expected by me, anyway :)
Well, at least is working, however is kinda an ugly fix. Could you
create the file /etc/modules-load.d/usb3.conf, with the line xhci in
it, reboot, and see if your little hack is not needed then? Also, if
you are using an initramfs, could you rebuild it before trying?
Alternatively, build xhci into the kernel, since you need it at every
boot.
Both of the suggestions above reversed the order of the journalctl
messages so that the usb3 drive appears before lvm.service is run,
but pvscan still finds no volumes and the volume group is not active
after bootup :(
I changed After=basic.target to After=sysinit.target, which still
gets it working well enough for my primitive needs. IMHO that fix
allows me to decrement ${HACKED} by one :)
Re: [gentoo-user] NFS kernel bug
On Sun, 08 Dec 2013 16:13:26 -0500 Tanstaafl tansta...@libertytrek.org wrote: On 2013-10-26 6:19 PM, Daniel Frey djqf...@gmail.com wrote: Just a note to other NFS server users - There's a kernel bug that can cause unmounting an NFS share to segfault (and not actually unmount anything.) I had in in the kernel 3.10 version, perhaps even before that as I don't update the kernel on my mythtv backend server that often. It hangs the shutdown process with an oops and it will require physical manual intervention to shut the machine down. If you upgrade to 3.11.5 or greater the problem goes away. I've been banging my head against the wall with this for over a week and *finally* found a resolution after going through a lot of NFS searches via Google. So... is this fixed in the stable 3.10 series (ie, 3.10.7 or 3.10.17)? TL;DR: One of both NFS fixes from 3.11.5 is fixed since v3.10.16, the other one is fixed since v3.11.5; porting the other one back does not appear easy, because different code is present (or an alternative fix). == Which commits? == http://thread.gmane.org/gmane.linux.kernel/1577607 mentions: 1. NFSv4.1: nfs4_fl_prepare_ds - fix bugs when the connect attempt fails 2. nfsd4: fix leak of inode reference on delegation failure == Are they present in v3.10.17? == For (1) we see that http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/?id=v3.10.17qt=grepq=nfs4_fl_prepare_ds does show the commit. For (2) we see that http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/?id=v3.10.17qt=grepq=fix%20leak%20of%20inode does not show the commit. So, one of both commits is fixed in 3.10.17, the other is not. == Which versions contain these commits? == We can find all relevant commits IDs by searching for the commit message in the last release of each branch; then we just enumerate all tags, which gives us the versions where the commit is present. Checking the upstream commits yields: $ git tag --contains 52b26a3e1bb3e065c32b3febdac1e1f117d88e15 # (1) v3.12 v3.12-rc4 v3.12-rc5 v3.12-rc6 v3.12-rc7 v3.12.1 v3.12.2 v3.12.3 v3.12.4 v3.13-rc1 v3.13-rc2 v3.13-rc3 $ git tag --contains bf7bd3e98be5c74813bee6ad496139fb0a011b3b # (2) v3.12 v3.12-rc1 v3.12-rc2 v3.12-rc3 v3.12-rc4 v3.12-rc5 v3.12-rc6 v3.12-rc7 v3.12.1 v3.12.2 v3.12.3 v3.12.4 v3.13-rc1 v3.13-rc2 v3.13-rc3 Checking the ported back 3.11 commits yields: $ git tag --contains 3b12032f89e27f139828bad8120149b1584bc898 # (1) v3.11.5 v3.11.6 v3.11.7 v3.11.8 v3.11.9 v3.11.10 $ git tag --contains ba3460519e393d0f212403ae3535305f423d84ed # (2) v3.11.5 v3.11.6 v3.11.7 v3.11.8 v3.11.9 v3.11.10 Checking the ported back 3.10 commit yields: $ git tag --contains 28f7ae257183e8064119db486190d2229caae369 # (1) v3.10.16 v3.10.17 v3.10.18 v3.10.19 v3.10.20 v3.10.21 v3.10.22 v3.10.23 This summarizes all versions where these two commits are available. == Only one of both is available in v3.10.17, can I apply the other? == It appears that (2) can't be applied to v3.10 without porting it back; or maybe it has already applied, but in a quite different way. == Which versions contain the bad commit(s)? Which one are affected? == A list of all versions that contain the bad commit of (2) are: $ git tag --contains 68a3396178e6688ad7367202cdf0af8ed03c8727 | tr '\n' ' ' v3.10 v3.10-rc1 v3.10-rc2 v3.10-rc3 v3.10-rc4 v3.10-rc5 v3.10-rc6 v3.10-rc7 v3.10.1 v3.10.10 v3.10.11 v3.10.12 v3.10.13 v3.10.14 v3.10.15 v3.10.16 v3.10.17 v3.10.18 v3.10.19 v3.10.2 v3.10.20 v3.10.21 v3.10.22 v3.10.23 v3.10.3 v3.10.4 v3.10.5 v3.10.6 v3.10.7 v3.10.8 v3.10.9 v3.11 v3.11-rc1 v3.11-rc2 v3.11-rc3 v3.11-rc4 v3.11-rc5 v3.11-rc6 v3.11-rc7 v3.11.1 v3.11.10 v3.11.2 v3.11.3 v3.11.4 v3.11.5 v3.11.6 v3.11.7 v3.11.8 v3.11.9 v3.12 v3.12-rc1 v3.12-rc2 v3.12-rc3 v3.12-rc4 v3.12-rc5 v3.12-rc6 v3.12-rc7 v3.12.1 v3.12.2 v3.12.3 v3.12.4 v3.13-rc1 v3.13-rc2 v3.13-rc3 Excluding wherever it is fixed, only v3.10-rc1 - v3.10.23 are affected. As the first commit doesn't mention where it regressed, I cannot check in which versions that bad commit is present for (1); though it is definitely limited to versions lower than v3.10.16 as evidenced earlier. -- With kind regards, Tom Wijsman (TomWij) Gentoo Developer E-mail address : tom...@gentoo.org GPG Public Key : 6D34E57D GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D signature.asc Description: PGP signature
Re: [gentoo-user] Re: [systemd] lvm.service running too early? [HACKED--]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/12/13 09:36, walt wrote:
On 12/08/2013 10:39 AM, Neil Bothwick wrote:
On Sun, 8 Dec 2013 11:12:23 -0600, Canek Peláez Valdés wrote:
It has the same problem. I looked more carefully at the systemd logs
and found that lvm was running before the xhci kernel module was
loaded, hence the usb3 drive was not visible yet.
I fixed the problem by adding After=basic to the lvm.service
file, and now it works as expected. (Expected by me, anyway :)
Well, at least is working, however is kinda an ugly fix. Could you
create the file /etc/modules-load.d/usb3.conf, with the line xhci in
it, reboot, and see if your little hack is not needed then? Also, if
you are using an initramfs, could you rebuild it before trying?
Alternatively, build xhci into the kernel, since you need it at every
boot.
Both of the suggestions above reversed the order of the journalctl
messages so that the usb3 drive appears before lvm.service is run,
but pvscan still finds no volumes and the volume group is not active
after bootup :(
I changed After=basic.target to After=sysinit.target, which still
gets it working well enough for my primitive needs. IMHO that fix
allows me to decrement ${HACKED} by one :)
Just a thought, but isn't there a unit file for autoloading modules
(therefore making it usable as a After= target)?
- --
Sam Jorna
sam.t.jo...@gmail.com
GnuPG Key ID: 12D3EE0C
Fingerprint:
6D14 8366 16F5 638E 3A29
1FED 5D5C 62D9 12D3 EE0C
Secure your E-mail:
http://www.gnupg.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.15 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQGcBAEBAgAGBQJSpQM3AAoJEF1cYtkS0+4MrI8MAKGdzdY5GLDwk1+1JF+DGMiC
RzHrrEVS/+bf8q/z8VSjFPvsIaML9x2yu/Iw2ucvFoFpk4D3n3DGBZrpRhEJiH5a
rj/caeoSH6Hs3qId+AAPfCLMl2cnAT1SdbmKnL1B+kHDdi3fPVgbIlJPjOIVUJ4J
JOh6/56iSSGo3xlwvRwii3su3xHFYYqs9YpTrJzFxaLL/sNIreiUDzA6wkB/BNEX
WvSXAXE7LLt7xo2CvMSU5uGhiCp0rR2iEUbGvZ08fkLLqZn4EGU97fzB7OQ5J6km
70yty45f4Sx55zwYTd7ekpTC0prl8dn8xlwARchmVaByBvIrbu1u+zeEYhvKf7G+
cYWKQ3y1VRCVBDWkLRrn6S2tUwDTCLGyzpLWMcl26oc9rguJ0ZUT7BL0zN0p5cfd
gJ6VZ9MsiXGgv1U3bduBGV7AQUREHQpItdM7z9kjKcEjqaILJX9FLluDDwhTHfcr
bIcRDPj+m8kdZvtznY7MWjoSp1RhOJlhaDbSpVXz+g==
=PWbf
-END PGP SIGNATURE-
Re: [gentoo-user] Re: [systemd] lvm.service running too early? [HACKED--]
On Sun, Dec 8, 2013 at 4:36 PM, walt w41...@gmail.com wrote:
On 12/08/2013 10:39 AM, Neil Bothwick wrote:
On Sun, 8 Dec 2013 11:12:23 -0600, Canek Peláez Valdés wrote:
It has the same problem. I looked more carefully at the systemd logs
and found that lvm was running before the xhci kernel module was
loaded, hence the usb3 drive was not visible yet.
I fixed the problem by adding After=basic to the lvm.service
file, and now it works as expected. (Expected by me, anyway :)
Well, at least is working, however is kinda an ugly fix. Could you
create the file /etc/modules-load.d/usb3.conf, with the line xhci in
it, reboot, and see if your little hack is not needed then? Also, if
you are using an initramfs, could you rebuild it before trying?
Alternatively, build xhci into the kernel, since you need it at every
boot.
Both of the suggestions above reversed the order of the journalctl
messages so that the usb3 drive appears before lvm.service is run,
but pvscan still finds no volumes and the volume group is not active
after bootup :(
Sounds like another module is then missing at early boot up time. Do
you have CONFIG_BLK_DEV_DM compiled in-kernel, or as a module? What
about the other CONFIG_DM_* options?
If they are modules, put them in a /etc/modules-load.d/*.config file.
I changed After=basic.target to After=sysinit.target, which still
gets it working well enough for my primitive needs. IMHO that fix
allows me to decrement ${HACKED} by one :)
Not editing unit files would be best, I think.
Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México
Re: [gentoo-user] Re: [systemd] lvm.service running too early? [HACKED--]
On Sun, Dec 8, 2013 at 5:39 PM, Sam Jorna sam.t.jo...@gmail.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/12/13 09:36, walt wrote:
On 12/08/2013 10:39 AM, Neil Bothwick wrote:
On Sun, 8 Dec 2013 11:12:23 -0600, Canek Peláez Valdés wrote:
It has the same problem. I looked more carefully at the systemd logs
and found that lvm was running before the xhci kernel module was
loaded, hence the usb3 drive was not visible yet.
I fixed the problem by adding After=basic to the lvm.service
file, and now it works as expected. (Expected by me, anyway :)
Well, at least is working, however is kinda an ugly fix. Could you
create the file /etc/modules-load.d/usb3.conf, with the line xhci in
it, reboot, and see if your little hack is not needed then? Also, if
you are using an initramfs, could you rebuild it before trying?
Alternatively, build xhci into the kernel, since you need it at every
boot.
Both of the suggestions above reversed the order of the journalctl
messages so that the usb3 drive appears before lvm.service is run,
but pvscan still finds no volumes and the volume group is not active
after bootup :(
I changed After=basic.target to After=sysinit.target, which still
gets it working well enough for my primitive needs. IMHO that fix
allows me to decrement ${HACKED} by one :)
Just a thought, but isn't there a unit file for autoloading modules
(therefore making it usable as a After= target)?
That's what /etc/modules-load.d is for:
http://www.freedesktop.org/software/systemd/man/modules-load.d.html
Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México
[gentoo-user] Any good way to pick global USE flag alternatives?
Can't come up with a more descriptive title for this one. The issue is this: There are some global USE flags that allow users to pick alternative methods of implementing the same thing. For example, packages that offer a GUI might do so through the qt or gtk USE flag. Or audio support, where you can choose alsa or pulseaudio. Now, if I wanted to, for example, always choose PulseAudio support instead of ALSA and a Qt GUI instead of a Gtk+ one, one would think that I could just do: USE=pulseaudio qt -alsa -gtk in my make.conf. But, that doesn't work. That's because some packages don't offer an alternative at all. Some package might only support ALSA for audio, and disabling that would lead to the package not offering any audio output at all. Or it might only offer a Gtk+ GUI, not a Qt one, and disabling the gtk flag will make the package not building its GUI component at all. So what's needed here, is a way to tell Portage to only disable a global USE flag for packages that also offer another one, specified by the user. Like this pseudo make.conf syntax: USE=pulseaudio pulseaudio?(-alsa) qt qt?(-gtk) Is something like this already possible? Right now, the only way to painstakingly go through every single package that comes up on an 'USE=use_flags_here emerge -pDN @world' and insert them individually into package.use. There should be a proper way of doing this.
Re: [gentoo-user] Any good way to pick global USE flag alternatives?
On 09/12/2013 08:25, Nikos Chantziaras wrote: Can't come up with a more descriptive title for this one. The issue is this: There are some global USE flags that allow users to pick alternative methods of implementing the same thing. For example, packages that offer a GUI might do so through the qt or gtk USE flag. Or audio support, where you can choose alsa or pulseaudio. Now, if I wanted to, for example, always choose PulseAudio support instead of ALSA and a Qt GUI instead of a Gtk+ one, one would think that I could just do: USE=pulseaudio qt -alsa -gtk in my make.conf. But, that doesn't work. That's because some packages don't offer an alternative at all. Some package might only support ALSA for audio, and disabling that would lead to the package not offering any audio output at all. Or it might only offer a Gtk+ GUI, not a Qt one, and disabling the gtk flag will make the package not building its GUI component at all. So what's needed here, is a way to tell Portage to only disable a global USE flag for packages that also offer another one, specified by the user. Like this pseudo make.conf syntax: USE=pulseaudio pulseaudio?(-alsa) qt qt?(-gtk) Is something like this already possible? Right now, the only way to painstakingly go through every single package that comes up on an 'USE=use_flags_here emerge -pDN @world' and insert them individually into package.use. There should be a proper way of doing this. There is no extant way to do what you want to do. USE flags operate in isolation and their end result is strictly limited to their own scope. Doing what you suggest leads to horrible breakage as the flag is no longer doing what you think it is doing, it is now possibly doing something quite different. Portage is already doing this properly. The correct way to deal with this (if there is such a thing) is in the package's own build system. That so few do such things is in itself telling. -- Alan McKinnon alan.mckin...@gmail.com
[gentoo-user] Re: Any good way to pick global USE flag alternatives?
On 09/12/13 08:56, Alan McKinnon wrote: On 09/12/2013 08:25, Nikos Chantziaras wrote: There are some global USE flags that allow users to pick alternative methods of implementing the same thing. For example, packages that offer a GUI might do so through the qt or gtk USE flag. Or audio support, where you can choose alsa or pulseaudio. Now, if I wanted to, for example, always choose PulseAudio support instead of ALSA and a Qt GUI instead of a Gtk+ one, one would think that I could just do: USE=pulseaudio qt -alsa -gtk in my make.conf. But, that doesn't work. [...] So what's needed here, is a way to tell Portage to only disable a global USE flag for packages that also offer another one, specified by the user. Like this pseudo make.conf syntax: USE=pulseaudio pulseaudio?(-alsa) qt qt?(-gtk) There should be a proper way of doing this. There is no extant way to do what you want to do. USE flags operate in isolation and their end result is strictly limited to their own scope. Doing what you suggest leads to horrible breakage as the flag is no longer doing what you think it is doing, it is now possibly doing something quite different. But it's already possible to do this through package.use. All I'm asking for is support for doing this in an automated way, without me needing to set USE flags in package.use for each package individually. Also, what exactly would this break? I can't think of any breakage because of this. Portage is already doing this properly. It's not doing it at all. The correct way to deal with this (if there is such a thing) is in the package's own build system. That so few do such things is in itself telling. That would be against Gentoo policy. Packages should offer build time configurations options for this, they shouldn't introduce automagic deps by checking what's available on your system. And that wouldn't work anyway; PulseAudio needs ALSA, so the build system would detect it anyway.
