1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
|
# IMPORTANT: In order to parse this new format, you need Portage 1.6 or later!
# OK; you're staring at this file and you have no idea what these stars are
# for. Here's the scoop. An initial "*" marks a package that is part of the
# official "base" system profile. If there's a "*", then "emerge system" will
# use the line in its calculations of what "should" be installed for this
# profile. Lines without a "*" prefix will be ignored for profile calculations.
# Now, this is new: *all* lines (star or no star) will be used as a special
# package *inclusion* mask. For example, the line *=sys-devel/gcc-2.95.3-r1
# will cause Portage to totally ignore all gcc ebuilds other than
# gcc-2.95.3-r1. >=, <=, <, > and ~ can be used to offer a bit more
# flexibility. For example, >=sys-libs/glibc-2.2.4 will cause emerge to ignore
# all glibc ebuilds with a version less than 2.2.4. This allows us to have
# profile-specific package.mask settings. *All* lines are used for this
# masking process, whether they are prefixed with a * or not. And if a generic
# dep is used, like "sys-apps/foo", then all versions of foo are included. If
# there is no entry, then all versions of an app are included. The key thing
# to note is that this file does not need to end up being an exhaustive list
# of portage packages; just the ones critical to this profile.
# So, what happens to /usr/portage/profiles/package.mask? It's still around,
# and still useful. But it should mainly be used for broken ebuilds only.
# package.mask continues to function as normal, masking out ebuilds from *all*
# system profiles.
# Which to use? Use the profile-specific stuff to "lock down" specific
# versions of ebuilds. Gentoo Linux 1.4 uses certain known-compatible
# versions of binutils, gcc and glibc, so we lock them down here. This
# prevents the user from shooting himself/herself in the foot by installing a
# wacky version.
# s390 Profile
# These don't make sense on s390
!sys-devel/bin86
!sys-boot/lilo
!sys-boot/grub
!dev-util/gtk-doc
# s390 specfic pkgs
*sys-apps/s390-tools
*virtual/bootloader
*dev-util/dialog
*>=sys-apps/baselayout-1.8.5.5
*>=sys-apps/portage-2.0.45-r2
*>=sys-devel/binutils-2.13.90.0.16
*>=sys-devel/gcc-3.2.3-r2
*>=sys-libs/glibc-2.3.2-r10
>=sys-kernel/linux-headers-2.4.21-r1
>=sys-apps/sysklogd-1.4.1
*dev-lang/python
*app-shells/sash
*dev-lang/perl
*virtual/editor
*net-ftp/ftp
*net-misc/iputils
*net-misc/rsync
*net-misc/wget
*app-shells/bash
*app-arch/bzip2
*sys-apps/kbd
*app-arch/cpio
*sys-apps/coreutils
*sys-apps/debianutils
*sys-apps/diffutils
*sys-fs/e2fsprogs
*sys-apps/ed
*sys-apps/fbset
*sys-apps/file
*sys-apps/findutils
*sys-apps/slocate
*sys-apps/gawk
*sys-apps/grep
*sys-apps/groff
*app-arch/gzip
*sys-apps/less
*sys-apps/man
*sys-apps/man-pages
*sys-apps/modutils
*sys-apps/net-tools
*sys-apps/procps
*sys-apps/psmisc
*sys-apps/sed
*sys-apps/setserial
*<sys-apps/shadow-5
*sys-apps/pam-login
*app-arch/sharutils
*app-arch/tar
*>=sys-apps/texinfo-4.2-r1
*sys-apps/util-linux
*sys-apps/which
*sys-devel/autoconf
*>=sys-devel/automake-1.6.1-r5
*sys-devel/bc
*sys-devel/bison
*sys-devel/flex
*sys-devel/gettext
*>=sys-devel/libtool-1.4.1-r4
*sys-devel/m4
*sys-devel/make
*sys-devel/patch
*sys-libs/cracklib
*sys-libs/db
*sys-libs/gdbm
*>=sys-libs/ncurses-5.2.20020511-r3
*>=sys-libs/pam-0.75-r10
*sys-libs/pwdb
*sys-libs/readline
*sys-libs/slang
*sys-libs/zlib
*net-misc/openssh
*virtual/dev-manager
|
GitWeb