Gentoo Logo
Gentoo Spaceship

Get Started
Gentoo Handbook
Downloads

News
Security Announcements
Calendar
Infrastructure Status

Documentation
Gentoo Handbook
Featured Documentation
IBM dW/Intel article archive

Get Gentoo
Downloads
Mirrors

Community
Discussion Forums
IRC Channels
Mailing Lists
Report Issues
Planet (Blogs)
Online Package Database
Wiki
Contact Us
Sponsors

Get Involved
Report Issues
Help Wanted
Help maintaining packages
Discussion Forums
IRC Channels
Mailing Lists
Become a Developer
Offer Resources
Enhancement Proposals (GLEPs)
Source Repositories
Developer's Manual

Other
Developer List
Developer Map
Gentoo Stores
Projects

About
About Gentoo
Philosophy
Social Contract
Name and Logo Guidelines
Logos and themes
Screenshots



Final step taken in migration to smaller, better Portage tree
Posted on February 4, 2008 by Donnie Berkholz

tux

Each ebuild in the Portage tree used to come with its own digest file. When you emerged a package, this digest was used to verify that you had the same files the developer did.

A few days ago, all digest files were erased from the Portage tree in CVS as part of the final work to implement GLEP 44. This migrates that information to a single Manifest file per package instead of one digest for every ebuild of that package. Portage hasn't been downloading these digest files for about a year, so this won't reduce the size of your tree again (it shrunk by ~200M at the time).

If you're still stuck on a Portage version in the 2.0.x series, follow the guide below on how to temporarily get Manifest1 files so you can update your Portage to the 2.1.x series.

References:

Discuss this!

Łukasz Damentko and Joshua Nichols contributed the draft for this announcement.

Correction: This was just the final step in a long-term migration that actually reduced the size of your Portage tree last February. Thanks to Daniel Drake, Petteri Räty and Jan Kundrat for pointing this out.




Page updated February 4, 2008

Donate to support our development efforts.

Copyright 2001-2014 Gentoo Foundation, Inc. Questions, Comments? Contact us.