| 1 |
On 8/23/2014 8:16 AM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 2 |
> On 23/08/2014 12:34, Tanstaafl wrote: |
| 3 |
>> Is it possible to do this? |
| 4 |
|
| 5 |
> Not directly. I'm assuming you mean packages you built yourself and |
| 6 |
> quick-pkg'ed them, not something available as a -bin |
| 7 |
|
| 8 |
Correct... I have buildpkg feature enabled in make.conf, so everything |
| 9 |
gets quickpkg'd... |
| 10 |
|
| 11 |
> You can use emerge -K, so emerge will fail if there's no binpkg |
| 12 |
> available. This will do what you want as long as you |
| 13 |
> |
| 14 |
> a) always use the -K option |
| 15 |
> b) don't try emerge something else as well |
| 16 |
> |
| 17 |
> Portage is designed to build your packages from source; binpkgs are very |
| 18 |
> much a third class citizen with only very primitive levels of support. |
| 19 |
|
| 20 |
Bummer... |
| 21 |
|
| 22 |
What I want is to be able to pin a specific package to the quickpkg'd |
| 23 |
version, so it doesn't get updated during an emerge world... |
Archives