Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 101922 - Suggestion: remove version specific packages in profiles
Summary: Suggestion: remove version specific packages in profiles
Status: RESOLVED INVALID
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Enhancement/Feature Requests (show other bugs)
Hardware: All Linux
: High enhancement
Assignee: Gentoo Release Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-09 17:55 UTC by Adam Jannetta
Modified: 2005-11-03 07:56 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Jannetta 2005-08-09 17:55:17 UTC
I think the version specific packages should be removed from the profiles so
when doing a stage 1 install the system will bootstrap the latest stable
packages.  For example, in /profiles/default-linux/x86/2005.1/packages there are
version specific  packages which are outdated and get bootstrapped unless
changed to newer versions.  My systems still bootstrap successfully when using
the latest stable versions. Correct me if they're like this for a reason.  I'm
not sure what the behavior is on arch's other than x86.

Reproducible: Always
Steps to Reproduce:
1.Do a stage 1 install.
2.Watch bootstrap.sh emerge older packages than the ones that are currently stable
3.Try removing version information in the packages file of your profile.
4.Bootstrap again and watch newer versions be compiled.

Actual Results:  
The system still bootstrapped successfully.
Comment 1 Alec Warner (RETIRED) archtester gentoo-dev Security 2005-08-09 18:00:20 UTC
Not sure who this goes to...but it's not a portage bug.
Comment 2 SpanKY gentoo-dev 2005-08-09 18:01:29 UTC
the versioned packages should be fine, no idea what you're talking about really
Comment 3 Adam Jannetta 2005-08-09 20:57:26 UTC
When a user goes and bootstraps their system the latest stable versions of the
packages aren't installed.  Instead, the ones specified in the packages file are.
Comment 4 SpanKY gentoo-dev 2005-08-09 21:05:51 UTC
that doesnt make any sense, the version strings are '>=' which means everything
newer or equal to that version should be utilized
Comment 5 Adam Jannetta 2005-08-12 15:16:37 UTC
Well when I bootstrap my systems, the versions that are installed are the ones
listed in the packages file even though >= is used.
Comment 6 Chris Gianelloni (RETIRED) gentoo-dev 2005-11-03 07:56:40 UTC
Really?

inertia 2005.1 # cat packages | grep binutils
>=sys-devel/binutils-2.15.90.0.3-r4
inertia 2005.1 # pwd
/mnt/gentoo/usr/portage/profiles/default-linux/x86/2005.1

inertia log # cat emerge.log | grep binutils
1131021567:  *** emerge  virtual/os-headers sys-apps/texinfo gettext
>=sys-devel/binutils-2.15.90.0.3-r4 >=sys-devel/gcc-3.3.4-r1 virtual/libc
>=sys-apps/baselayout-1.11.12-r4 sys-libs/zlib
1131022034:  >>> emerge (4 of 8) sys-devel/binutils-2.15.92.0.2-r10 to /
1131022034:  === (4 of 8) Cleaning
(sys-devel/binutils-2.15.92.0.2-r10::/usr/portage/sys-devel/binutils/binutils-2.15.92.0.2-r10.ebuild)
1131022035:  === (4 of 8) Compiling/Merging
(sys-devel/binutils-2.15.92.0.2-r10::/usr/portage/sys-devel/binutils/binutils-2.15.92.0.2-r10.ebuild)
inertia log # pwd
/mnt/gentoo/var/log

Looks to me like portage is using the latest stable version.