108263 – split portage into separate packages

Bug 108263 - split portage into separate packages

Summary: split portage into separate packages

Status:	RESOLVED LATER

Alias:	None

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

Importance:	High normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2005-10-06 05:21 UTC by Jason Stubbs (RETIRED)
Modified:	2007-01-10 03:35 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 Jason Stubbs (RETIRED) gentoo-dev

2005-10-06 05:21:18 UTC

* portage (emerge/emerge-webrsync/env-update/quickpkg/etc) 
* etc-update 
* dispatch-conf 
* repoman (+ ebuild?) 
 
whatever else can be separated...

Comment 1 Brian Harring (RETIRED) gentoo-dev

2005-10-12 21:39:51 UTC

I'd be curious how repoman is going to be maintained against portage, since the
two aren't exactly seperate entities.

Comment 2 Zac Medico gentoo-dev

2005-10-17 22:02:27 UTC

While portage.config has some PORTAGE_CALLER==repoman specific code in, the
dependency is nonetheless unidirectional.  What is to stop repoman from being
distributed as a separate package with it's own release schedule?

Comment 3 Marius Mauch (RETIRED) gentoo-dev

2006-02-16 17:43:09 UTC

I can see repoman being a separate package (or maybe part of gentoolkit-dev), and maybe moving dispatch-conf to gentoolkit, but I don't see etc-update being removed from portage itself (said it in the past, I dislike having separate packages for helper scripts, and etc-update is just that).

Comment 4 Marius Mauch (RETIRED) gentoo-dev

2007-01-10 03:35:26 UTC

Don't see this happening anytime soon.