Profile for cobalt mips machines. Cobalt's are mips little-endian systems

and as such need a separate profile for things to work properly.

1 files changed, 103 insertions, 0 deletions

diff --git a/profiles/cobalt-mips-1.4/packages b/profiles/cobalt-mips-1.4/packages
new file mode 100644
index 000000000000..727ace87e440
--- /dev/null
+++ b/profiles/cobalt-mips-1.4/packages
@@ -0,0 +1,103 @@
+# 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.0_rc6 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.
+!dev-lang/gpc
+
+# Core Packages
+*>=sys-apps/baselayout-1.8.6
+*>=sys-apps/portage-2.0.45
+*>=sys-devel/binutils-2.14.90.0.2
+*>=sys-devel/gcc-3.2.2
+*>=sys-libs/glibc-2.3.2-r1
+*>=sys-kernel/mips-headers-2.4.21
+*>=sys-devel/gnuconfig-20030708
+
+# Not in portage yet
+# Controls the front LCD panel
+*>=sys-apps/lcdutils
+
+>=sys-apps/sysklogd-1.4.1
+*dev-lang/python
+*app-shells/sash
+*dev-lang/perl
+*virtual/editor
+*net-misc/dhcpcd
+*net-misc/rsync
+*net-misc/wget
+*net-misc/iputils
+*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/gawk
+*sys-apps/grep
+*sys-apps/groff
+*app-arch/gzip
+*sys-apps/hdparm
+*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-r5
+*sys-apps/util-linux
+*sys-apps/which
+*sys-devel/autoconf
+*>=sys-devel/automake-1.6.1-r6
+*sys-devel/bc
+*sys-devel/bison
+*sys-devel/flex
+*>=sys-devel/libtool-1.4.1-r9
+*sys-devel/m4
+*sys-devel/make
+*sys-devel/patch
+*sys-libs/cracklib  
+*sys-libs/db
+*>=sys-libs/ncurses-5.2-r2
+*sys-libs/pam     
+*sys-libs/pwdb      
+*sys-libs/readline  
+*sys-libs/zlib
+*net-misc/openssh
+*sys-fs/devfsd