[gentoo-user] Re: using package.provided

[gentoo-user] Re: using package.provided

[reader]

Alan McKinnon <alan@linuxholdings.co.za> writes:

>> I ask because setting a higher version number might eventually need
>> bumping still higher... or if versioning changes somehow will
>> `higher' not be noticed.
>
> If you want to maintain and use old package-1.0.0 by yourself, and there 
> is already package-2.3 in the portage tree, then you need to mask out 
> any version greater than your custom ebuild. So, you put this 
> in /etc/portage/package.mask:

Thanks for the tips on other areas too, but the above tip clears up
something I've had wrong for some time.  

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: using package.provided

[reader]

Neil Bothwick <neil@digimed.co.uk> writes:

> While package.provided does have some genuine uses, one of its main
> functions is to provide people who don't fully understand it with a simple
> way of producing hard to diagnose system breakages :(

Very good.... Made my day.

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: using package.provided

[reader]

Alan McKinnon <alan@linuxholdings.co.za> writes:

> This section is snipped [from -sic]  one of Allen M. posts
                                              ^^^^^
Please excuse the misspelling

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: using package.provided

[reader]

Alan McKinnon <alan@linuxholdings.co.za> writes:

> You need to learn more about portage. Read:
>
> man portage
> man 5 portage
> man ebuild
> man 5 ebuild

Now I have a better idea how things are meant to work... but if I want
to violate that... by that I mean ..not work on my own ebuild enough
to begin to understand how its done... not put in the time and effort
required to do my own ebuild.

I like to build my own emacs, I've used emacs since about 1996, Long
before I started with gentoo (about 2 yrs now ago).

I like where a default emacs build and install puts stuff, I like the
emacs maintainers ideas of preloaded stuff.  I don't want to find some
buried package conflict due to something gentoo devs think should be
preloaded or whatever.

I have a long list of special lisp packages in places I expect.
I update from cvs often.

In short I prefer not having to even think about all the above. 
I prefer the simplicity of hand installation and know exactly what to
expect.  

cd /usr/local/cvs/emacs and cvs update -Pd
./configure
make 
make install

All that said, what then would be the best way to let gentoo know I
have installed a very recent emacs and any dependancies gentoo may
need are available at /usr/local/share/emacs.

I've been doing it by putting this in
/etc/portage/profile/package.provided

  app-editors/emacs-cvs-24
  app-editors/emacs-24

(not sure if the double entry matters)

Is it correct that at least theoretically:
When emacs passes version 24 gentoo would then begin installing emacs
from portage?

Is that likely to fall victim to Neils humorous point about causing
hard to diagnose system problems?

Is there a better way to accomplish my goal?  The masking approach was
explained as being a way to continue to use OLDER packages which is
not the case here.

-- 
gentoo-user@gentoo.org mailing list

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

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 570 bytes --]

On Fri, 22 Dec 2006 11:05:40 -0600, reader@newsguy.com wrote:

> All that said, what then would be the best way to let gentoo know I
> have installed a very recent emacs and any dependancies gentoo may
> need are available at /usr/local/share/emacs.
> 
> I've been doing it by putting this in
> /etc/portage/profile/package.provided
> 
>   app-editors/emacs-cvs-24
>   app-editors/emacs-24

Yes, that's just the sort of situation package.provided is intended for.


-- 
Neil Bothwick

Shell to DOS... Shell to DOS... DOS, do you copy? Shell to DOS...

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-user] using package.provided

[Harry Putnam]

I'd like to stay on kernel-4.1.6, rather than keep installing the
newest version at each upgrade.

As I recall, and a quick look at `man portage', a file named
`package.provided' is meant for such things.

The syntax is not described in detail... I tried these:

  /etc/portage/package.provided

  >=sys-kernel/gentoo-sources-4.1.6

Still `emerge -vp gentoo-sources' indicates it will install the most
recent kernel.

then I noticed the portage man page, under `Format' does say:
"relational operators are not allowed"
So I dropped the `>=' part

  sys-kernel/gentoo-sources-4.1.6

Same result from `emerge -vp gentoo-sources' . . .

What am I forgetting?

Re: [gentoo-user] using package.provided

[Dale]

Harry Putnam wrote:
> I'd like to stay on kernel-4.1.6, rather than keep installing the
> newest version at each upgrade.
>
> As I recall, and a quick look at `man portage', a file named
> `package.provided' is meant for such things.
>
> The syntax is not described in detail... I tried these:
>
>   /etc/portage/package.provided
>
>   >=sys-kernel/gentoo-sources-4.1.6
>
> Still `emerge -vp gentoo-sources' indicates it will install the most
> recent kernel.
>
> then I noticed the portage man page, under `Format' does say:
> "relational operators are not allowed"
> So I dropped the `>=' part
>
>   sys-kernel/gentoo-sources-4.1.6
>
> Same result from `emerge -vp gentoo-sources' . . .
>
> What am I forgetting?
>
>
>


This is how I do this sort of thing.  I add the name and version to
package.mask which stops future updates/upgrades.  Example, for my
nvidia drivers, this is in package.mask.

>=x11-drivers/nvidia-drivers-341.0.0 

That tells portage that anything above that version is masked locally
and not to update it.  For what you want, this should work:

>sys-kernel/gentoo-sources-4.1.6

I removed the equal sign since you want to keep that version around but
nothing above it.  If portage doesn't like that, you may want to use the
next version up and have the ">=" in front.  According to what I have
here, it would be like this:

>=sys-kernel/gentoo-sources-4.1.12 

I actually don't show a 4.1.6 here right now.  Removed I guess but
likely still works.

That goes under /etc/portage/ by the way.  I think you know that already
but just in case.  I have those moments too.  ;-) 

That helps??

Dale

:-)  :-) 

Re: [gentoo-user] using package.provided

[Dale]

Dale wrote:
> Harry Putnam wrote:
>> I'd like to stay on kernel-4.1.6, rather than keep installing the
>> newest version at each upgrade.
>>
>> As I recall, and a quick look at `man portage', a file named
>> `package.provided' is meant for such things.
>>
>> The syntax is not described in detail... I tried these:
>>
>>   /etc/portage/package.provided
>>
>>   >=sys-kernel/gentoo-sources-4.1.6
>>
>> Still `emerge -vp gentoo-sources' indicates it will install the most
>> recent kernel.
>>
>> then I noticed the portage man page, under `Format' does say:
>> "relational operators are not allowed"
>> So I dropped the `>=' part
>>
>>   sys-kernel/gentoo-sources-4.1.6
>>
>> Same result from `emerge -vp gentoo-sources' . . .
>>
>> What am I forgetting?
>>
>>
>>
>
> This is how I do this sort of thing.  I add the name and version to
> package.mask which stops future updates/upgrades.  Example, for my
> nvidia drivers, this is in package.mask.
>
>> =x11-drivers/nvidia-drivers-341.0.0 
> That tells portage that anything above that version is masked locally
> and not to update it.  For what you want, this should work:
>
>> sys-kernel/gentoo-sources-4.1.6
> I removed the equal sign since you want to keep that version around but
> nothing above it.  If portage doesn't like that, you may want to use the
> next version up and have the ">=" in front.  According to what I have
> here, it would be like this:
>
>> =sys-kernel/gentoo-sources-4.1.12 
> I actually don't show a 4.1.6 here right now.  Removed I guess but
> likely still works.
>
> That goes under /etc/portage/ by the way.  I think you know that already
> but just in case.  I have those moments too.  ;-) 
>
> That helps??
>
> Dale
>
> :-)  :-) 
>
>

I was triple checking and realized something.  Some of the lines are not
correct.  It seems in my email software at least it puts a little line
in place of the >.  So, let me try this way.  


Nvidia is like this:  >=x11-drivers/nvidia-drivers-341.0.0

Your kernel line may work like this:  >sys-kernel/gentoo-sources-4.1.6

Or it may have to be like this if portage doesn't like the above: 
>=sys-kernel/gentoo-sources-4.1.12

Now, let's see if that displays correctly.  I won't know until I send it
and get it back. 

Dale

:-)  :-) 

Re: [gentoo-user] using package.provided

[Dale]

Dale wrote:
> Dale wrote:
>> Harry Putnam wrote:
>>> I'd like to stay on kernel-4.1.6, rather than keep installing the
>>> newest version at each upgrade.
>>>
>>> As I recall, and a quick look at `man portage', a file named
>>> `package.provided' is meant for such things.
>>>
>>> The syntax is not described in detail... I tried these:
>>>
>>>   /etc/portage/package.provided
>>>
>>>   >=sys-kernel/gentoo-sources-4.1.6
>>>
>>> Still `emerge -vp gentoo-sources' indicates it will install the most
>>> recent kernel.
>>>
>>> then I noticed the portage man page, under `Format' does say:
>>> "relational operators are not allowed"
>>> So I dropped the `>=' part
>>>
>>>   sys-kernel/gentoo-sources-4.1.6
>>>
>>> Same result from `emerge -vp gentoo-sources' . . .
>>>
>>> What am I forgetting?
>>>
>>>
>>>
>> This is how I do this sort of thing.  I add the name and version to
>> package.mask which stops future updates/upgrades.  Example, for my
>> nvidia drivers, this is in package.mask.
>>
>>> =x11-drivers/nvidia-drivers-341.0.0 
>> That tells portage that anything above that version is masked locally
>> and not to update it.  For what you want, this should work:
>>
>>> sys-kernel/gentoo-sources-4.1.6
>> I removed the equal sign since you want to keep that version around but
>> nothing above it.  If portage doesn't like that, you may want to use the
>> next version up and have the ">=" in front.  According to what I have
>> here, it would be like this:
>>
>>> =sys-kernel/gentoo-sources-4.1.12 
>> I actually don't show a 4.1.6 here right now.  Removed I guess but
>> likely still works.
>>
>> That goes under /etc/portage/ by the way.  I think you know that already
>> but just in case.  I have those moments too.  ;-) 
>>
>> That helps??
>>
>> Dale
>>
>> :-)  :-) 
>>
>>
> I was triple checking and realized something.  Some of the lines are not
> correct.  It seems in my email software at least it puts a little line
> in place of the >.  So, let me try this way.  
>
>
> Nvidia is like this:  >=x11-drivers/nvidia-drivers-341.0.0
>
> Your kernel line may work like this:  >sys-kernel/gentoo-sources-4.1.6
>
> Or it may have to be like this if portage doesn't like the above: 
>> =sys-kernel/gentoo-sources-4.1.12
> Now, let's see if that displays correctly.  I won't know until I send it
> and get it back. 
>
> Dale
>
> :-)  :-) 
>


Silly software.  That bottom line wraps here so it took it out like the
first email did.  So, if it is doing the same for you, that bottom line
needs a greater than sign in front of the category and package name. 
Let's see if it edits out the words "greater than sign" as well.  ROFL  
The biggest thing, I think you want to use package.mask anyway.  That
should help. 

Jeez.  Sometimes I want to take a hammer to a puter. 

Dale

:-)  :-)

Re: [gentoo-user] using package.provided

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1323 bytes --]

On Wed, 24 Feb 2016 22:55:30 -0500, Harry Putnam wrote:

> I'd like to stay on kernel-4.1.6, rather than keep installing the
> newest version at each upgrade.
> 
> As I recall, and a quick look at `man portage', a file named
> `package.provided' is meant for such things.

No it's not. package.provided is for when you install a package from
outside of portage and want to let portage know it is installed.

> The syntax is not described in detail... I tried these:
> 
>   /etc/portage/package.provided

The file is /etc/portage/profile/package.provided
> 
>   >=sys-kernel/gentoo-sources-4.1.6  

and it only allows specific atoms, =cat/pkg

> Still `emerge -vp gentoo-sources' indicates it will install the most
> recent kernel.

You want to use /etc/portage/package.mask, with this entry

    >sys-kernel/gentoo-sources-4.1.6

One of the disadvantages of this is that when that particular version is
removed from the tree, portage will try to downgrade, because you has
blocked an upgrade. To avoid this, copy the ebuild to a local overlay so
it is always available.

You'll also miss out on any security updates etc, but I guess you have
already considered that.


-- 
Neil Bothwick

If Wile E. Coyote had enough money to buy all that ACME crap, why didn't
he just buy dinner?

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] using package.provided

[covici]

Dale <rdalek1967@gmail.com> wrote:

> Harry Putnam wrote:
> > I'd like to stay on kernel-4.1.6, rather than keep installing the
> > newest version at each upgrade.
> >
> > As I recall, and a quick look at `man portage', a file named
> > `package.provided' is meant for such things.
> >
> > The syntax is not described in detail... I tried these:
> >
> >   /etc/portage/package.provided
> >
> >   >=sys-kernel/gentoo-sources-4.1.6
> >
> > Still `emerge -vp gentoo-sources' indicates it will install the most
> > recent kernel.
> >
> > then I noticed the portage man page, under `Format' does say:
> > "relational operators are not allowed"
> > So I dropped the `>=' part
> >
> >   sys-kernel/gentoo-sources-4.1.6
> >
> > Same result from `emerge -vp gentoo-sources' . . .
> >
> > What am I forgetting?
> >
> >
> >
> 
> 
> This is how I do this sort of thing.  I add the name and version to
> package.mask which stops future updates/upgrades.  Example, for my
> nvidia drivers, this is in package.mask.
> 
> >=x11-drivers/nvidia-drivers-341.0.0 
> 
> That tells portage that anything above that version is masked locally
> and not to update it.  For what you want, this should work:
> 
> >sys-kernel/gentoo-sources-4.1.6
> 
> I removed the equal sign since you want to keep that version around but
> nothing above it.  If portage doesn't like that, you may want to use the
> next version up and have the ">=" in front.  According to what I have
> here, it would be like this:
> 
> >=sys-kernel/gentoo-sources-4.1.12 
> 
> I actually don't show a 4.1.6 here right now.  Removed I guess but
> likely still works.
> 
> That goes under /etc/portage/ by the way.  I think you know that already
> but just in case.  I have those moments too.  ;-) 
> 
> That helps??

I think its in /etc/portage/profile instead.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] using package.provided

[Dale]

covici@ccs.covici.com wrote:
> Dale <rdalek1967@gmail.com> wrote:
>
>> Harry Putnam wrote:
>>> I'd like to stay on kernel-4.1.6, rather than keep installing the
>>> newest version at each upgrade.
>>>
>>> As I recall, and a quick look at `man portage', a file named
>>> `package.provided' is meant for such things.
>>>
>>> The syntax is not described in detail... I tried these:
>>>
>>>   /etc/portage/package.provided
>>>
>>>   >=sys-kernel/gentoo-sources-4.1.6
>>>
>>> Still `emerge -vp gentoo-sources' indicates it will install the most
>>> recent kernel.
>>>
>>> then I noticed the portage man page, under `Format' does say:
>>> "relational operators are not allowed"
>>> So I dropped the `>=' part
>>>
>>>   sys-kernel/gentoo-sources-4.1.6
>>>
>>> Same result from `emerge -vp gentoo-sources' . . .
>>>
>>> What am I forgetting?
>>>
>>>
>>>
>>
>> This is how I do this sort of thing.  I add the name and version to
>> package.mask which stops future updates/upgrades.  Example, for my
>> nvidia drivers, this is in package.mask.
>>
>>> =x11-drivers/nvidia-drivers-341.0.0 
>> That tells portage that anything above that version is masked locally
>> and not to update it.  For what you want, this should work:
>>
>>> sys-kernel/gentoo-sources-4.1.6
>> I removed the equal sign since you want to keep that version around but
>> nothing above it.  If portage doesn't like that, you may want to use the
>> next version up and have the ">=" in front.  According to what I have
>> here, it would be like this:
>>
>>> =sys-kernel/gentoo-sources-4.1.12 
>> I actually don't show a 4.1.6 here right now.  Removed I guess but
>> likely still works.
>>
>> That goes under /etc/portage/ by the way.  I think you know that already
>> but just in case.  I have those moments too.  ;-) 
>>
>> That helps??
> I think its in /etc/portage/profile instead.
>


Mine here is in:  /etc/portage/package.mask  It's been there for a long
time.  Maybe they are moving things again to something new but it works
here. 

Dale

:-)  :-) 

[gentoo-user] Re: using package.provided

[Nikos Chantziaras]

On 25/02/16 05:55, Harry Putnam wrote:
> I'd like to stay on kernel-4.1.6, rather than keep installing the
> newest version at each upgrade.

I'd instead recommend putting

   >=sys-kernel/gentoo-sources-4.2

in package.mask to stay with 4.1 (it's an LTS kernel) and always get the 
patches for that one.

Re: [gentoo-user] using package.provided

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 503 bytes --]

On Thu, 25 Feb 2016 15:47:32 -0600, Dale wrote:

> Mine here is in:  /etc/portage/package.mask  It's been there for a long
> time.  Maybe they are moving things again to something new but it works
> here. 

Things that override global settings in make.conf, like package.mask, go
in /etc/portage. Things that override profile settings go
in /etc/portage/profile.

If in doubt, read man portage which explains all these files.


-- 
Neil Bothwick

Only an idiot actually READS taglines.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] using package.provided

[Dale]

Neil Bothwick wrote:
> On Thu, 25 Feb 2016 15:47:32 -0600, Dale wrote:
>
>> Mine here is in:  /etc/portage/package.mask  It's been there for a long
>> time.  Maybe they are moving things again to something new but it works
>> here. 
> Things that override global settings in make.conf, like package.mask, go
> in /etc/portage. Things that override profile settings go
> in /etc/portage/profile.
>
> If in doubt, read man portage which explains all these files.
>
>


All I know, it works here.  What the OP is wanting to do is no different
than what I am doing here except that it is a different package.  So, if
it works here, it should work there too.  I might add, I don't even have
the profile directory at all. 

Dale

:-)  :-) 

Re: [gentoo-user] using package.provided

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 916 bytes --]

On Fri, 26 Feb 2016 03:39:22 -0600, Dale wrote:

> >> Mine here is in:  /etc/portage/package.mask  It's been there for a
> >> long time.  Maybe they are moving things again to something new but
> >> it works here.   
> > Things that override global settings in make.conf, like package.mask,
> > go in /etc/portage. Things that override profile settings go
> > in /etc/portage/profile.
> >
> > If in doubt, read man portage which explains all these files.

> All I know, it works here.  What the OP is wanting to do is no different
> than what I am doing here except that it is a different package.  So, if
> it works here, it should work there too.  I might add, I don't even have
> the profile directory at all. 

But then you don't use package.provided. If you did, it wouldn't work
unless it was in /etc/portage/profile.


-- 
Neil Bothwick

I wouldn't be caught dead with a necrophiliac.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] using package.provided

[Dale]

Neil Bothwick wrote:
> On Fri, 26 Feb 2016 03:39:22 -0600, Dale wrote:
>
>>>> Mine here is in:  /etc/portage/package.mask  It's been there for a
>>>> long time.  Maybe they are moving things again to something new but
>>>> it works here.   
>>> Things that override global settings in make.conf, like package.mask,
>>> go in /etc/portage. Things that override profile settings go
>>> in /etc/portage/profile.
>>>
>>> If in doubt, read man portage which explains all these files.
>> All I know, it works here.  What the OP is wanting to do is no different
>> than what I am doing here except that it is a different package.  So, if
>> it works here, it should work there too.  I might add, I don't even have
>> the profile directory at all. 
> But then you don't use package.provided. If you did, it wouldn't work
> unless it was in /etc/portage/profile.
>
>

Although the OP asked about package.provided, it isn't what he needs to
use.  As you pointed out in another reply, he needs package.mask and it
goes in /etc/portage/.  It doesn't really matter if the OP has a profile
directory or not since he doesn't need to use that in this case.  He
just needs to use package.mask and add the correct info there.  After
that, the OP is done. 

Dale

:-)  :-) 

[gentoo-user] Re: using package.provided

[Harry Putnam]

First off, thanks to all posters for the excellent input

> Nikos Chantziaras <realnc@gmail.com> writes:

> On 25/02/16 05:55, Harry Putnam wrote:
>> I'd like to stay on kernel-4.1.6, rather than keep installing the
>> newest version at each upgrade.
>
> I'd instead recommend putting
>
>   >=sys-kernel/gentoo-sources-4.2
>
> in package.mask to stay with 4.1 (it's an LTS kernel) and always get
> the patches for that one.

In /etc/portage/package-mask, using the line you suggest:

  >=sys-kernel/gentoo-sources-4.2

Makes emerge want to install 4.1.18:

  emerge -vp gentoo-sources
   [...]
  Calculating dependencies... done!
  [ebuild  NS    ] sys-kernel/gentoo-sources-4.1.18:4.1.18::gentoo
  [4.1.6:4.1.6::gentoo] USE="-build -experimental -kdbus -symlink" 575 KiB

Using `>=sys-kernel/gentoo-sources-4.1.6'
emerge wants to install 4.0.9:

   [ebuild  NS    ] sys-kernel/gentoo-sources-4.0.9:4.0.9::gentoo
   [...]

Using `>sys-kernel/gentoo-sources-4.1.6'
emerge want to install 4.0.9 as well

  [ebuild  NS    ] sys-kernel/gentoo-sources-4.0.9:4.0.9::gentoo [...]

So apparently none of the suggestions causes emerge to just stay with 4.1.6    

-------       -------       ---=---       -------       -------

However, after creating /etc/portage/profile and placing
package.provided with `sys-kernel/gentoo-sources-4.1.6' inside.
(NOTE:package.provided does not allow any <,>,= type signs)

root # emerge -vp gentoo-sources

  These are the packages that would be merged, in order:

  Calculating dependencies... done!

  Total: 0 packages, Size of downloads: 0 KiB

  WARNING: A requested package will not be merged because it is listed in
  package.provided:

  gentoo-sources pulled in by 'args'

This appears to do what I was after.  Should I expect any `gotchas'?

[gentoo-user] Re: using package.provided

[Nikos Chantziaras]

On 26/02/16 18:47, Harry Putnam wrote:
> First off, thanks to all posters for the excellent input
>
>> Nikos Chantziaras <realnc@gmail.com> writes:
>
>> On 25/02/16 05:55, Harry Putnam wrote:
>>> I'd like to stay on kernel-4.1.6, rather than keep installing the
>>> newest version at each upgrade.
>>
>> I'd instead recommend putting
>>
>>    >=sys-kernel/gentoo-sources-4.2
>>
>> in package.mask to stay with 4.1 (it's an LTS kernel) and always get
>> the patches for that one.
>
> In /etc/portage/package-mask, using the line you suggest:
>
>    >=sys-kernel/gentoo-sources-4.2
>
> Makes emerge want to install 4.1.18:

Yes, which is what I recommended. Don't block 4.1.x security/bugfix 
patches. Just block 4.2 and above.

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

[Rich Freeman]

On Fri, Feb 26, 2016 at 4:15 PM, Nikos Chantziaras <realnc@gmail.com> wrote:
>
> Yes, which is what I recommended. Don't block 4.1.x security/bugfix patches.
> Just block 4.2 and above.
>

++

4.1 is a longterm series, so if your goal is minimum disruption you
can stay on it until Sep 2017.  I would still recommend taking the
4.1.x updates both for backports and possible security updates.

I personally just have my own git tree.  It is easy to just update it
in place vs unpacking huge tarballs every time there is a patch
release, and I'm less-tied to the Gentoo maintainers.  They do a great
job, but since I run btrfs I tend to be really picky about what kernel
series I'm on.

The one thing I'd love to see upstreamed is the openrc/systemd/etc
convenience configuration items.

-- 
Rich

[gentoo-user] Re: using package.provided

[Harry Putnam]

Nikos Chantziaras <realnc@gmail.com> writes:

> On 26/02/16 18:47, Harry Putnam wrote:
>> First off, thanks to all posters for the excellent input
>>
>>> Nikos Chantziaras <realnc@gmail.com> writes:
>>
>>> On 25/02/16 05:55, Harry Putnam wrote:
>>>> I'd like to stay on kernel-4.1.6, rather than keep installing the
>>>> newest version at each upgrade.
>>>
>>> I'd instead recommend putting
>>>
>>>    >=sys-kernel/gentoo-sources-4.2
>>>
>>> in package.mask to stay with 4.1 (it's an LTS kernel) and always get
>>> the patches for that one.
>>
>> In /etc/portage/package-mask, using the line you suggest:
>>
>>    >=sys-kernel/gentoo-sources-4.2
>>
>> Makes emerge want to install 4.1.18:
>
> Yes, which is what I recommended. Don't block 4.1.x security/bugfix
> patches. Just block 4.2 and above.

Ahh... now I get what your saying..  Some of your previous comments
slid right over my thick skull.  Thank you.