245779 – buildpkg location changes from portage 2.1 to 2.2

Bug 245779 - buildpkg location changes from portage 2.1 to 2.2

Summary: buildpkg location changes from portage 2.1 to 2.2

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Documentation (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:	InVCS

Depends on:
Blocks:	210077
	Show dependency tree

Reported:	2008-11-06 04:54 UTC by edoceo
Modified:	2008-11-22 05:54 UTC (History)
CC List:	1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description edoceo 2008-11-06 04:54:49 UTC

In portage 2.1 when using buildpkg the files are created in 
 /usr/portage/packages/All/syslog-ng-2.0.9.tbz
and symlinked point here is created as 
 /usr/portage/packages/app-admin/syslog-ng-2.0.9.tbz

In portage 2.2 it only makes
 /usr/portage/packages/app-admin/syslog-ng-2.0.9.tbz

The documentation (that is man page) does not reflect this change in Portage operation.  The man page in question is man 1 ebuild.

I don't know how to make patches for man pages otherwise I'd attach one.

Comment 1 Zac Medico gentoo-dev

2008-11-07 04:10:56 UTC

Both layouts are still supported. If the $PKGDIR/All/ directory exists then the old layout is used, except in cases when collisions need to be resolved in order to avoid bug #133908.

Comment 2 Zac Medico gentoo-dev

2008-11-22 05:54:18 UTC

This is fixed in 2.2_rc15.