On Fri, Mar 31, 2006 at 12:19:32PM +0200, Pascal Bleser wrote:
> - YOU: online updates: packages provided by SUSE to fix security 
> issues and sometimes severe bug fixes. No feature upgrades, only for 
> security fixes.
> - update: well... that's what is kind of missing in yast2 (to do it, 
> it's like I described in my previous mail). It's just when you want to 
> have the latest available version of some or all packages that are 
> installed on your system.
> - upgrade: upgrade the whole distribution, e.g. from 10.0 to 10.1

There should be also a YOU for additional repo's. I asume the reason it
won't work now is that YOU only looks at 1 URL. I personally want my
system as close to SUSE as possible, wich means I do not use newer
versions from e.g. Packman. The sole reason I do this is because I am too
lazy to look if any packages need a security update.

I select the SUSE packages and only use e.g. the Pasckman packages if
something does not work.

> You don't want to have the latest version of everything. Really, you 
> don't. And even if you think you want that, you don't.

Concerning updates: If it ain't broke, don't fix it. On Usenet I always
ask the question WHY people do a certain update (e.g. aa KDE update) and
in about 90% that an answer is given, people don't know. Also most people
do not know that when they do an update, that YOU won't update that
package.

e.g. update from Firefox 1.0 to 1.5. Day that a security leak is found in
6 months. My 1.0 will be patched by SUSE (Thanks guys and girls) most
peoples 1.5 won't be patched, because they asume YOU will do it for them.

A YOU for addidtional repo's would help solve that. I hope once the new
build server is installed and I can point their, that this will become
possible.

<snip good explanation>
> Do you really want that ? I don't think so ;)

People who DO want it; run Factory. :-)

> >*what packages are changed by an update?
> 
> Those that you select when you say that you want to update them.

With YOU you don selct anything (or all). I asume that is what he talked
about. With YOU all packages that you have installed _and_ have an update
available will be updated with YOU.

> >Probably it should be worth to have a list of all the
> >packages ever used in SUSE (raw) with a quotation mark in
> >the distro number (column-or better the version number).
> 
> You gotta be kidding. Why don't you do it yourself ?

It would be nice to have this done on the SUSE side.
software.openSUSE.org. Everybody then could see what SUSE version has what
software version, including the Beta's

I am not sure how hard it would be to make such a thing. I can immagine
people might be interested in this, although I personaly could not care
less what version my slrn or mutt or whatever is running.

If SUSE has something like this already, perhaps it is possible to put it
in a public database in one form or another.

As an extra, you could tell on what media it is. e.g. CD4 or only FTP.
The data is already available on line for the current production prduct:
http://www.novell.com/products/linuxpackages/professional/index.html
Again: having a public accesible database sounds like a good idea.

> >may be it could be worth a database app with entried for
> >packages, versions (initial, last updated), SUSE versions.
> >but I don't know how to integrate this in the wiki (by the
> >way don't Novell/Suse have already such data???)
> 
> That can be done from the INDEX.gz file that's on every SUSE Linux CD, 
> it has a list of all packages (of all files on the media, actually).

It might be better to use the one from the FTP site, because the one on
the CD only has the the content from the CD.

houghi
-- 
Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es 
ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk
und Arbeit,  und das Sein wichtiger als das Tun                                 
                                        - Johannes Müller-Elmau

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to