16026 – Request: --unstable portage flag

Bug 16026 - Request: --unstable portage flag

Summary: Request: --unstable portage flag

Status:	RESOLVED DUPLICATE of bug 14741

Alias:	None

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

Importance:	High enhancement (vote)
Assignee:	Nicholas Jones (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2003-02-19 15:08 UTC by Francisco León
Modified:	2011-10-30 22:18 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 Francisco León 2003-02-19 15:08:52 UTC

I just had an idea, maybe you will like it.
emerge -up world could have a flag called --unstable that it would 
automatically enable ~x86 or your arch so it would show the latest versions of 
portage.

Also, emerge package --unstable could install the latest package in the portage 
tree. That way we wouldn't have to edit make.conf every time...

Emerge -s package --unstable would show the latest unstable build on portage 
too... You get the idea

So, what do you think? Seems easy to implement.

Reproducible: Always
Steps to Reproduce:
1.n/a
2.
3.

Actual Results:  
n/a

Expected Results:  
n/a

Comment 1 SpanKY gentoo-dev

2003-02-19 15:50:59 UTC


*** This bug has been marked as a duplicate of 14741 ***

Comment 2 Daniel Willmann 2003-07-03 09:49:51 UTC

In Bug# 23861 I creadted a patch, that has the requested functionality.