Re: [gentoo-user] Re: package.provided syntax for overlay

[Mick]

On Monday 20 Feb 2017 13:23:15 Neil Bothwick wrote:
> On Mon, 20 Feb 2017 14:07:39 +0100, Kai Krakow 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?  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 ...  :-/
> > 
> > You could package.mask */*::bar and then only unmask the needed bits.
> 
> That does seem a cleaner way of doing it. When I first did this, that
> option wasn't available.

Thank you both, eventually I used Kai's suggestion, rather than having to mask 
a package at a time that entrance was pulling in as dependencies.

Entrance works fine, other than the pam config it ships with which is not 
working at all on a non-gnome gentoo system.  I need to brush up on pam, which 
I have been avoiding it seems forever and this may be the excuse I needed to 
do it.
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Re: package.provided syntax for overlay

[Neil Bothwick]

On Mon, 20 Feb 2017 14:07:39 +0100, Kai Krakow 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?  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 ...  :-/  
> 
> You could package.mask */*::bar and then only unmask the needed bits.

That does seem a cleaner way of doing it. When I first did this, that
option wasn't available.


-- 
Neil Bothwick

Hell:  Filling out the paperwork to get into Heaven.


pgpZwx8JL4T4K.pgp
Description: OpenPGP digital signature

[gentoo-user] Re: package.provided syntax for overlay

[Kai Krakow]

Am Sun, 19 Feb 2017 10:20:41 +
schrieb Mick :

> 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?

The file needs to go to /etc/portage/profile/package.provided to have
any effect. But I guess this is the wrong way for what you're going to
accomplish. You should instead mask that version and then see, what
pulls it in. Or you could try the world upgrade with "--exclude
enlightenment" switch.

-- 
Regards,
Kai

Replies to list-only preferred.


pgpkf2CxgORn5.pgp
Description: Digitale Signatur von OpenPGP

[gentoo-user] Re: package.provided syntax for overlay

[Kai Krakow]

Am Sun, 19 Feb 2017 11:17:11 +
schrieb Mick :

> On Sunday 19 Feb 2017 10:50:31 Neil Bothwick wrote:
> > On Sun, 19 Feb 2017 11:45:27 +0100, Johannes Rosenberger wrote:  
>  [...]  
> > > 
> > > 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 ...  :-/

You could package.mask */*::bar and then only unmask the needed bits.

-- 
Regards,
Kai

Replies to list-only preferred.


pgpbWadLvkH5f.pgp
Description: Digitale Signatur von OpenPGP

Re: [gentoo-user] Re: package.provided syntax

[Rumen Yotov]

On Monday 06 March 2006 21:09, Harry Putnam wrote:
 Zac Medico [EMAIL PROTECTED] writes:
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

 Ok, I'm a little gun shy to post this now but I'm still seeing
 somethign screwy.

 cat /etc/portage/package.provided
 app-backup/rsnapshot-1.2.2
 app-backup/bacula-1.48.5
 app-editors/emacs-cvs-24

 emerge -vp 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


 Man portage mentions a version must be included:
  Format:
  - comments begin with #
  - one DEPEND atom per line
  - relational operators are not allowed
  - must include a version

 It also says:
   . . . . . . Portage will  not  attempt  to  update  a
   package  that  is  listed  here  unless  another  package
   explicitly requires a version that is newer than what has
   been  listed.

 So I thought maybe it didn't like my fake version so changed it to:

app-editors/emacs-cvs-22.0.50-r1
 And I still get the same output.

 Removing the -r1 since its not really emacs versioning and I still get
 the same output...
 Something is making emerge ignore this package.provided
Hi,
In my case (using it a little but think it works) the file is in other dir:
# cat /etc/portage/profile/package.provided
app-admin/fam-2.7.0-r2
Only now i see that forgot to change this (left from fam-- gamin conversion).
HTH.Rumen


pgpigpRKlY2YJ.pgp
Description: PGP signature

Re: [gentoo-user] Re: package.provided syntax

[Zac Medico]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Harry Putnam wrote:
 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
 
 Ok, I'm a little gun shy to post this now but I'm still seeing
 somethign screwy.
 
 cat /etc/portage/package.provided

Oops, package.provided goes in /etc/portage/profile/ (it's an override for 
/etc/make.profile).  That's probably a common mistake.


 app-backup/rsnapshot-1.2.2
 app-backup/bacula-1.48.5
 app-editors/emacs-cvs-24
 
 emerge -vp 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

Hmm, the emerge output indicates that app-editors/emacs-cvs-22.0.50 is 
installed (managed by portage).  Normally package.provided is used for packages 
that aren't managed by portage.  Now I'm not sure what you want to accomplish.

Zac
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (GNU/Linux)

iD8DBQFEDT/V/ejvha5XGaMRAuY5AJ9zVGlkeL+bjPhaA52m4d5edJQWlwCg44l7
x4iYA2CCaPYiLxTkqp7y29g=
=otXv
-END PGP SIGNATURE-
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: package.provided syntax

[Harry Putnam]

Rumen Yotov [EMAIL PROTECTED] writes:


[...]

 Hi,
 In my case (using it a little but think it works) the file is in other dir:
 # cat /etc/portage/profile/package.provided
 app-admin/fam-2.7.0-r2

Zac Medico [EMAIL PROTECTED] writes:
 Oops, package.provided goes in /etc/portage/profile/ (it's an
 override for /etc/make.profile).  That's probably a common mistake.

Thanks posters... yup, no wonder it was being ignored eh?
All better now.

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: package.provided syntax

[Harry Putnam]

Dave Nebinger [EMAIL PROTECTED] writes:

 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?

Gack.. not a typo a braino

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: package.provided syntax

[Harry Putnam]

Zac Medico [EMAIL PROTECTED] writes:

 app-backup/rsnapshot-1.2.2
 app-backup/bacula-1.48.5
 app-editors/emacs-cvs-24

Haa there it is 
Another dopey message was sent before I saw this, and the real sorry
part is that I've been caught by this before and not too long ago.

I've recently done a full reinstall from scratch and when I redid that
part I forgot about it again...

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: package.provided syntax

[Harry Putnam]

Zac Medico [EMAIL PROTECTED] writes:

   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

Ok, I'm a little gun shy to post this now but I'm still seeing
somethign screwy.

cat /etc/portage/package.provided
app-backup/rsnapshot-1.2.2
app-backup/bacula-1.48.5
app-editors/emacs-cvs-24

emerge -vp 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


Man portage mentions a version must be included:
 Format:
 - comments begin with #
 - one DEPEND atom per line
 - relational operators are not allowed
 - must include a version

It also says:
  . . . . . . Portage will  not  attempt  to  update  a
  package  that  is  listed  here  unless  another  package
  explicitly requires a version that is newer than what has
  been  listed.

So I thought maybe it didn't like my fake version so changed it to:

   app-editors/emacs-cvs-22.0.50-r1
And I still get the same output.  

Removing the -r1 since its not really emacs versioning and I still get
the same output...
Something is making emerge ignore this package.provided

-- 
gentoo-user@gentoo.org mailing list