| 1 |
Mark Knecht wrote: |
| 2 |
> On Tue, Jan 27, 2009 at 6:00 PM, Nikos Chantziaras <realnc@×××××.de> wrote: |
| 3 |
>> In order to reduce clutter in the keyword files, you can omit the "~amd64" |
| 4 |
>> part. This is equvalent: |
| 5 |
>> |
| 6 |
>> =dev-libs/glib-2.18.4 |
| 7 |
>> |
| 8 |
>> Also, it helps explaining to people how to keyword packages without knowing |
| 9 |
>> their arch. |
| 10 |
> |
| 11 |
> Makes sense. By giving the exact package revision I'm saying that's |
| 12 |
> the one I want. I don't need any additional wild card of any type. |
| 13 |
> |
| 14 |
> Additionally is address my other frustrating with this where I want |
| 15 |
> and need some version, say 2.18.1, so I use ~amd64 to get it, and then |
| 16 |
> over time the system builds 2.18.2, 2.18.3, 2.18.4, etc., which I |
| 17 |
> don't need and personalyl don't want until one of them goes stable. |
| 18 |
|
| 19 |
To only have 2.18.1 you use this: |
| 20 |
|
| 21 |
<dev-libs/glib-2.18.2 |
| 22 |
|
| 23 |
That means "only versions lower than 2.18.2". That way, portage will |
| 24 |
never update to 2.18.2 or higher if it's not marked stable. Valid |
| 25 |
"operators" are: =, <, >, <= and >=. |
| 26 |
|
| 27 |
Normally, one would think that it's better to use this: |
| 28 |
|
| 29 |
<=dev-libs/glib-2.18.1 |
| 30 |
|
| 31 |
to achieve the same result. However, it's usually good to get revision |
| 32 |
bumps (for example 2.18.1-r1) since they're meant to fix bugs. With |
| 33 |
"<dev-libs/glib-2.18.2" you'll never get 2.18.2 if it's not marked |
| 34 |
stable, but you'll still get 2.18.1-rN revision bumps which should be a |
| 35 |
good thing. |
Archives