21447 – Portagemaster dependency fix suggestion

Bug 21447 - Portagemaster dependency fix suggestion

Summary: Portagemaster dependency fix suggestion

Status:	RESOLVED FIXED

Alias:	None

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

Importance:	Lowest trivial (vote)
Assignee:	Portage Tools Team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2003-05-21 17:34 UTC by Carl Olof Englund
Modified:	2011-10-30 22:21 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 Carl Olof Englund 2003-05-21 17:34:10 UTC

Portagemaster seems to want me to download SUNs JDK. Since I prefer Blackdown
I'm not too happy about that. Emergeing with -O got around the problem but would
it be possible to add a check in the ebuild for ANY previously installed JDK (or
JRE?) instead?

Comment 1 Tobias Minich 2003-08-31 05:46:38 UTC

I agree. The dependency statements should be fixed to say something like "virtual/jdk-1.4"

Comment 2 Marius Mauch (RETIRED) gentoo-dev

2003-11-20 10:25:52 UTC

I'm about to commit portagemaster-0.2.1 (as 0.2.0 produces a nasty IndexOutOfBoundsException), any reason why we should not change the jdk dependency ?

Comment 3 Adrian Almenar 2003-11-20 11:59:19 UTC

You can change it, but you have to test it with blackdown-(jdk|jre) at least.

Comment 4 Marius Mauch (RETIRED) gentoo-dev

2003-11-20 12:40:02 UTC

I bumped the 0.2.0 ebuild to 0.2.1 and changed the dependencies (tested with blackdown and sun-j2sdk), only for ~x86 though at the moment.