| 1 |
on Friday 01/19/2007 Norberto Bensa(nbensa@×××.net) wrote |
| 2 |
> Hello list, |
| 3 |
> |
| 4 |
> what does "~" mean here: |
| 5 |
> (example from /usr/portage/profiles/package.mask) |
| 6 |
> |
| 7 |
> ~net-dns/bind-tools-9.3.3 |
| 8 |
|
| 9 |
Excerpt from man 5 ebuild |
| 10 |
|
| 11 |
Now to get even fancier, we provide the ability to define |
| 12 |
blocking packages and version range matching. Also note |
| 13 |
that these extended prefixes/postfixes |
| 14 |
may be combined in any way with the atom classes defined |
| 15 |
above. Here are |
| 16 |
some common examples you may find in the |
| 17 |
portage tree: |
| 18 |
|
| 19 |
!app-text/dos2unix |
| 20 |
=dev-libs/glib-2* |
| 21 |
!=net-fs/samba-2* |
| 22 |
~net-libs/libnet-1.0.2a |
| 23 |
|
| 24 |
! means block packages from being |
| 25 |
installed at the same time. |
| 26 |
* means match any version of the package |
| 27 |
so long as the specified base is |
| 28 |
matched. So with a version of '2*', |
| 29 |
we |
| 30 |
can match '2.1', '2.2', '2.2.1', |
| 31 |
etc... and not match version '1.0', |
| 32 |
'3.0', '4.1', etc... |
| 33 |
~ means match any revision of the |
| 34 |
base version specified. So in the |
| 35 |
above example, we would match versions |
| 36 |
'1.0.2a', '1.0.2a-r1', '1.0.2a-r2', etc... |
| 37 |
|
| 38 |
|
| 39 |
Hope this helps. |
| 40 |
|
| 41 |
-- |
| 42 |
Your life is like a penny. You're going to lose it. The question is: |
| 43 |
How do |
| 44 |
you spend it? |
| 45 |
|
| 46 |
John Covici |
| 47 |
covici@××××××××××.com |
| 48 |
-- |
| 49 |
gentoo-user@g.o mailing list |
Archives