Bug 103771

Summary:	Daily RPM to add the latests package repository information to YaST
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Haakon Eriksen <haakon>
Component:	YOU	Assignee:	Adrian Schröter <adrian.schroeter>
Status:	RESOLVED WONTFIX	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Enhancement
Priority:	P5 - None	CC:	aj, binner, suse-beta
Version:	unspecified
Target Milestone:	---
Hardware:	i686
OS:	SuSE Pro 9.3
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Haakon Eriksen 2005-08-10 10:00:49 UTC

SuSE YOU includes only updates to a specific release, like the files shipped 
with SuSE 9.3. This approach excludes major updates to important user tools 
like KDE. The user must first find yast-sources by searching the web, add them 
to installation sources module, then start the installation module. It works 
great, but this can be done a lot better by having a daily RPM available 
through SuSE YOU with the latest official mirrors and yast-sources. They don't 
have to be turned on in the installation sources module, but this makes it a 
lot easier to find them and turn them on as needed.

Comment 1 Andreas Jaeger 2005-08-10 11:01:36 UTC

Interesting idea!  thanks.

Adrian, what do you think?

Comment 2 Haakon Eriksen 2005-08-12 06:54:13 UTC

/etc/youservers seems to something like this, but I don't like the description
enough to dare try it.

Comment 3 Christoph Thiel 2005-08-22 09:29:17 UTC

I'd rather like YaST to query some server to get the installation sources as 
needed, but on the whole it's something that we definitely need with the 
upcoming openSUSE "build infrastructure"...

Comment 4 Christoph Thiel 2005-09-04 11:51:28 UTC

Something for the SUSE Linux 10.1 timeframe.

Comment 5 Adrian Schröter 2005-10-17 09:38:05 UTC

it will not handled by YOU, because YOU is only for maintainance and this will not not change. But we will offer such a service via the openSUSE build enviroment.

However, there is some way to go before, but it is part of the requirements.

So we can close this bug so far, thanks for your suggestion.