[gentoo-user] Re: using package.provided

2016-02-27 Thread Harry Putnam
Nikos Chantziaras writes: > On 26/02/16 18:47, Harry Putnam wrote: >> First off, thanks to all posters for the excellent input >> >>> Nikos Chantziaras writes: >> >>> On 25/02/16 05:55, Harry Putnam wrote: I'd like to stay on kernel-4.1.6, rather than

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

2016-02-26 Thread Rich Freeman
On Fri, Feb 26, 2016 at 4:15 PM, Nikos Chantziaras 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

[gentoo-user] Re: using package.provided

2016-02-26 Thread Nikos Chantziaras
On 26/02/16 18:47, Harry Putnam wrote: First off, thanks to all posters for the excellent input Nikos Chantziaras 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

[gentoo-user] Re: using package.provided

2016-02-26 Thread Harry Putnam
First off, thanks to all posters for the excellent input > Nikos Chantziaras 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 > >

[gentoo-user] Re: using package.provided

2016-02-25 Thread 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

[gentoo-user] Re: using package.provided

2006-12-22 Thread reader
Alan McKinnon [EMAIL PROTECTED] 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

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

2006-12-22 Thread Neil Bothwick
On Fri, 22 Dec 2006 11:05:40 -0600, [EMAIL PROTECTED] 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

[gentoo-user] Re: using package.provided

2006-12-21 Thread reader
Alan McKinnon [EMAIL PROTECTED] 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

[gentoo-user] Re: using package.provided

2006-12-21 Thread reader
Neil Bothwick [EMAIL PROTECTED] 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

[gentoo-user] Re: using package.provided

2006-12-21 Thread reader
Alan McKinnon [EMAIL PROTECTED] writes: This section is snipped [from -sic] one of Allen M. posts ^ Please excuse the misspelling -- gentoo-user@gentoo.org mailing list