1 |
Hi All, |
2 |
|
3 |
Portage-1.5.1 has been released, and includes a couple of new features: |
4 |
|
5 |
= Config file management |
6 |
= The new "~foo/bar-1.0" dependency |
7 |
|
8 |
Config file management has been explained in an earlier email, but you may |
9 |
not know too much about the new ~ dependency. Here's how it works. |
10 |
|
11 |
~foo/bar-1.0 will match the *latest revision* of the foo/bar-1.0 package, but |
12 |
not any later version. So, it'll match 1.0-r5, but not 1.0.3 or 2.0 or even |
13 |
1.0_rc3. If you're creating ebuilds and depend on a *specific* version of |
14 |
foo/bar, it's generally best to now use ~ rather than = so that any new revs |
15 |
will get used automatically, since new revs usually contain bug fixes. = is |
16 |
still useful in things like package.mask, where you want to mask out a specific |
17 |
package and rev, and of course don't want your mask to automatically follow the |
18 |
latest available rev. |
19 |
|
20 |
I'd appreciate it if all developers could upgrade and try out this version; |
21 |
normal users should probably wait until Wednesday before upgrading. Developers, |
22 |
please only use ~ for testing for the time being, since these deps will be |
23 |
rejected by earlier versions of Portage. You should be able to use them in |
24 |
non-masked ebuilds in maybe a week and a half. |
25 |
|
26 |
Best Regards, |
27 |
|
28 |
-- |
29 |
Daniel Robbins <drobbins@g.o> |
30 |
President/CEO http://www.gentoo.org |
31 |
Gentoo Technologies, Inc. |