Re: [gentoo-user] package.provided syntax for overlay
On Sun, 19 Feb 2017 11:17:11 +, Mick wrote: > > Another option is to copy/symlink the specific package you want from > > the bar overlay to your local overlay and do not include the bar > > overlay in repos.conf. > > Sorry for being dense. Do you mean first add the overlay with 'layman > -a bar', then symlink the particular package to my local overlay? Yes. > How > will I be updating this package in the future, if I do not have the > 'bar' overlay settings in /etc/portage/repos.conf/layman.conf? Layman will still update all its overlays when you run layman -S, but portage will not see the contents. I've used this method often when I want a single package from an overlay. You may have to link more than one package to satisfy dependencies, but that is not usually the case in my experience. -- Neil Bothwick Where do you think you're going today? pgpNWlsu4j_Dd.pgp Description: OpenPGP digital signature
Re: [gentoo-user] package.provided syntax for overlay
On Sunday 19 Feb 2017 10:50:31 Neil Bothwick wrote: > On Sun, 19 Feb 2017 11:45:27 +0100, Johannes Rosenberger wrote: > > > So I tried in /etc/portage/package.provided any combination of these: > > > > > > x11-wm/enlightenment-:0.17/::bar > > > > > > =x11-wm/enlightenment-:0.17 > > > > > > x11-wm/enlightenment- > > > > > > None of which can stop portage dragging in 'x11- > > > wm/enlightenment-:0.17/::bar'. What is the correct syntax to > > > block this version of enlightenment from emerging? > > > > According to the portage manpage 'x11-wm/enlightenment-' should be > > the correct syntax. > > > > But I think, package.provided is the wrong file at all. The correct way > > to accomplish what you want to is masking > > 'x11-wm/enlightenment-:0.17/::bar'. > > Agreed. > > Another option is to copy/symlink the specific package you want from the > bar overlay to your local overlay and do not include the bar overlay in > repos.conf. Sorry for being dense. Do you mean first add the overlay with 'layman -a bar', then symlink the particular package to my local overlay? How will I be updating this package in the future, if I do not have the 'bar' overlay settings in /etc/portage/repos.conf/layman.conf? I'm trying to understand the benefit of doing it as you suggest above ... :-/ -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] package.provided syntax for overlay
On Sunday 19 Feb 2017 11:45:27 Johannes Rosenberger wrote: > On 19.02.2017 11:20, Mick wrote: > > Hi All, > > > > Given sddm is not working for my setup, as per bug #608690, I thought of > > trying entrance from the bar overlay. It wants to pull in enlightenment, > > which I have already installed from the main tree and would like to keep > > it as such: > > > > # emerge -uaDv entrance > > > > These are the packages that would be merged, in order: > > > > Calculating dependencies... done! > > [ebuild U ~] x11-wm/enlightenment-:0.17/::bar > > [0.20.6:0.17/0.20.6::gentoo] USE="eeze%* nls pam ukit -doc -egl% > > -pm-utils% - static-libs -systemd -wayland (-spell%*)" > > ENLIGHTENMENT_MODULES="appmenu backlight battery bluez4 clock > > conf-applications conf-bindings conf-dialogs conf-display > > conf-interaction conf-intl conf-menus conf-paths conf-performance > > conf-randr conf-shelves conf-theme conf-window-manipulation conf-window- > > remembers connman contact%* cpufreq everything fileman fileman-opinfo > > gadman ibar ibox lokker mixer msgbus music-control notification pager > > pager16%* quickaccess shot start syscon systray tasks teamwork > > temperature tiling winlist wizard xkbswitch -access% -packagkit% > > -wl-desktop-shell* -wl-drm* -wl- fb% -wl-x11* (-conf%*) (-geolocation%*) > > (-packagekit%*) (-pager-plain%*) (- policy-mobile%*) (-wl-text-input%*) > > (-wl-weekeyboard%*) (-wl-wl%*) (- xwayland%*)" 0 KiB > > [ebuild N*] x11-plugins/entrance-::bar USE="consolekit pam -grub > > - systemd -vkbd" 0 KiB > > > > > > So I tried in /etc/portage/package.provided any combination of these: > > > > x11-wm/enlightenment-:0.17/::bar > > > > =x11-wm/enlightenment-:0.17 > > > > x11-wm/enlightenment- > > > > None of which can stop portage dragging in 'x11- > > wm/enlightenment-:0.17/::bar'. What is the correct syntax to > > block > > this version of enlightenment from emerging? > > According to the portage manpage 'x11-wm/enlightenment-' should be > the correct syntax. > > But I think, package.provided is the wrong file at all. The correct way > to accomplish what you want to is masking > 'x11-wm/enlightenment-:0.17/::bar'. The problem with this > package is that it is keyworded incorrectly as '~amd64 ~x86' despite > being a live ebuild. > If you already have enlightenment:0.17 installed this should suffice, > since entrance only depends on this and not the live ebuild. Thank you Johannes, I removed package.provided and added '=x11- wm/enlightenment-:0.17' in package.mask. Now it wants to install: x11-wm/enlightenment-0.21.3:0.17/0.21::bar so I added that version in package.mask too and it now is emerging entrance. :-) -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] package.provided syntax for overlay
On Sun, 19 Feb 2017 11:45:27 +0100, Johannes Rosenberger wrote: > > So I tried in /etc/portage/package.provided any combination of these: > > > > x11-wm/enlightenment-:0.17/::bar > > > > =x11-wm/enlightenment-:0.17 > > > > x11-wm/enlightenment- > > > > None of which can stop portage dragging in 'x11- > > wm/enlightenment-:0.17/::bar'. What is the correct syntax to > > block this version of enlightenment from emerging? > > > According to the portage manpage 'x11-wm/enlightenment-' should be > the correct syntax. > > But I think, package.provided is the wrong file at all. The correct way > to accomplish what you want to is masking > 'x11-wm/enlightenment-:0.17/::bar'. Agreed. Another option is to copy/symlink the specific package you want from the bar overlay to your local overlay and do not include the bar overlay in repos.conf. -- Neil Bothwick Change is inevitable. Except from a vending machine. pgpqRAjluxWjL.pgp Description: OpenPGP digital signature
Re: [gentoo-user] package.provided syntax for overlay
On 19.02.2017 11:20, Mick wrote: > Hi All, > > Given sddm is not working for my setup, as per bug #608690, I thought of > trying entrance from the bar overlay. It wants to pull in enlightenment, > which I have already installed from the main tree and would like to keep it > as > such: > > # emerge -uaDv entrance > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > [ebuild U ~] x11-wm/enlightenment-:0.17/::bar > [0.20.6:0.17/0.20.6::gentoo] USE="eeze%* nls pam ukit -doc -egl% -pm-utils% - > static-libs -systemd -wayland (-spell%*)" ENLIGHTENMENT_MODULES="appmenu > backlight battery bluez4 clock conf-applications conf-bindings conf-dialogs > conf-display conf-interaction conf-intl conf-menus conf-paths > conf-performance > conf-randr conf-shelves conf-theme conf-window-manipulation conf-window- > remembers connman contact%* cpufreq everything fileman fileman-opinfo gadman > ibar ibox lokker mixer msgbus music-control notification pager pager16%* > quickaccess shot start syscon systray tasks teamwork temperature tiling > winlist wizard xkbswitch -access% -packagkit% -wl-desktop-shell* -wl-drm* -wl- > fb% -wl-x11* (-conf%*) (-geolocation%*) (-packagekit%*) (-pager-plain%*) (- > policy-mobile%*) (-wl-text-input%*) (-wl-weekeyboard%*) (-wl-wl%*) (- > xwayland%*)" 0 KiB > [ebuild N*] x11-plugins/entrance-::bar USE="consolekit pam -grub - > systemd -vkbd" 0 KiB > > > So I tried in /etc/portage/package.provided any combination of these: > > x11-wm/enlightenment-:0.17/::bar > > =x11-wm/enlightenment-:0.17 > > x11-wm/enlightenment- > > None of which can stop portage dragging in 'x11- > wm/enlightenment-:0.17/::bar'. What is the correct syntax to block > this version of enlightenment from emerging? > According to the portage manpage 'x11-wm/enlightenment-' should be the correct syntax. But I think, package.provided is the wrong file at all. The correct way to accomplish what you want to is masking 'x11-wm/enlightenment-:0.17/::bar'. The problem with this package is that it is keyworded incorrectly as '~amd64 ~x86' despite being a live ebuild. If you already have enlightenment:0.17 installed this should suffice, since entrance only depends on this and not the live ebuild.
[gentoo-user] package.provided syntax for overlay
Hi All, Given sddm is not working for my setup, as per bug #608690, I thought of trying entrance from the bar overlay. It wants to pull in enlightenment, which I have already installed from the main tree and would like to keep it as such: # emerge -uaDv entrance These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ~] x11-wm/enlightenment-:0.17/::bar [0.20.6:0.17/0.20.6::gentoo] USE="eeze%* nls pam ukit -doc -egl% -pm-utils% - static-libs -systemd -wayland (-spell%*)" ENLIGHTENMENT_MODULES="appmenu backlight battery bluez4 clock conf-applications conf-bindings conf-dialogs conf-display conf-interaction conf-intl conf-menus conf-paths conf-performance conf-randr conf-shelves conf-theme conf-window-manipulation conf-window- remembers connman contact%* cpufreq everything fileman fileman-opinfo gadman ibar ibox lokker mixer msgbus music-control notification pager pager16%* quickaccess shot start syscon systray tasks teamwork temperature tiling winlist wizard xkbswitch -access% -packagkit% -wl-desktop-shell* -wl-drm* -wl- fb% -wl-x11* (-conf%*) (-geolocation%*) (-packagekit%*) (-pager-plain%*) (- policy-mobile%*) (-wl-text-input%*) (-wl-weekeyboard%*) (-wl-wl%*) (- xwayland%*)" 0 KiB [ebuild N*] x11-plugins/entrance-::bar USE="consolekit pam -grub - systemd -vkbd" 0 KiB So I tried in /etc/portage/package.provided any combination of these: x11-wm/enlightenment-:0.17/::bar =x11-wm/enlightenment-:0.17 x11-wm/enlightenment- None of which can stop portage dragging in 'x11- wm/enlightenment-:0.17/::bar'. What is the correct syntax to block this version of enlightenment from emerging? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] package.provided syntax
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Harry Putnam wrote: > I'm currently trying to get thru an emerge -vuD world but having > various things crop up. Some I thought were handled long ago like > this overlooking what is in package.provided: > > rsnapshot-1.2.2 > bacula-1.48.5 > cvs-emacs-24 The example for package.provided syntax in `man portage` shows categories like this: app-backup/rsnapshot-1.2.2 app-backup/bacula-1.48.5 app-editors/emacs-cvs-24 And like Dave said, you have cvs-emacs rather than emacs-cvs. Zac > > The last two are fake versions so they would stay ahead of what ever > comes into portage for a while. My understanding is that portage > looks here, and if the version is newer it by passes these packages. > > So this should not happen: > > emerge -vuDp app-editors/emacs-cvs > These are the packages that would be merged, in order: > > Calculating dependencies... done! > [ebuild U ] app-editors/emacs-cvs-22.0.50-r1 [22.0.50] USE="X gif > gtk jpeg nls png spell -Xaw3d -tiff" 0 kB > > Oh, and why is `tiff' turned off (-tiff)? > > > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (GNU/Linux) iD8DBQFEDISR/ejvha5XGaMRAiiNAJ96sa0yTnYzsimB3MwzkgSaC5KeHQCeJaQt /siLLdvGc77aWlmKr4s+OxU= =7fXZ -END PGP SIGNATURE- -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] package.provided syntax
Harry Putnam wrote: in package.provided: cvs-emacs-24 [snip] emerge -vuDp app-editors/emacs-cvs Don't you see that cvs-emacs is not the same as emacs-cvs, or was this just a typo on your part? -- gentoo-user@gentoo.org mailing list
[gentoo-user] package.provided syntax
I'm currently trying to get thru an emerge -vuD world but having various things crop up. Some I thought were handled long ago like this overlooking what is in package.provided: rsnapshot-1.2.2 bacula-1.48.5 cvs-emacs-24 The last two are fake versions so they would stay ahead of what ever comes into portage for a while. My understanding is that portage looks here, and if the version is newer it by passes these packages. So this should not happen: emerge -vuDp app-editors/emacs-cvs These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] app-editors/emacs-cvs-22.0.50-r1 [22.0.50] USE="X gif gtk jpeg nls png spell -Xaw3d -tiff" 0 kB Oh, and why is `tiff' turned off (-tiff)? -- gentoo-user@gentoo.org mailing list