On 2006/12/21 17:18 (GMT+0100) Andreas Hanke apparently typed:

> Felix Miata schrieb:

>> The inexplicable part is that the base tree doesn't contain everything
>> pertaining to a particular release:

>> This:
>> http://ftp.suse.com/pub/suse/update/10.2/

>> Should be:
>> http://ftp.suse.com/pub/opensuse/update/10.2/

>> Because:
>> http://ftp.opensuse.org/pub/opensuse/distribution/10.2/

>> Is not:
>> http://ftp.opensuse.org/pub/suse/distribution/10.2/

> Why?

> ftp.suse.com is /suse/, ftp.opensuse.org is /opensuse/.

Yet another artificial distinction, obfuscation worthy of M$. No one
whose mind works logically expects to find updates for a distribution
whose home is ftp.opensuse.org on ftp.suse.com, unless one is a mere
symlink for the other, which in this case is untrue, as only the latter
has updates for the releases whose apparent home is ftp.opensuse.org.
ftp.suse.com is the logical place to find only updates for non-open suse
products, not for opensuse products.

> The mirror thing is not a problem either, the base distribution is
> separated from the update tree because mirrors don't necessarily want to
> have everything.

Then follow Mandriva's lead:
Up to higher level directory
Directory: 10.0                 04/05/24        00:00:00
Directory: 10.1                 04/12/01        00:00:00
Directory: 10.2                 05/10/14        00:00:00
Directory: 2005                 06/11/07        17:40:00
Directory: 2006.0               05/10/18        00:00:00
Directory: 2007.0               06/09/22        13:21:00
Directory: 9.1          03/10/16        00:00:00
Directory: 9.2          03/10/13        00:00:00
Directory: current              06/11/08        05:48:00
Directory: iso          06/10/10        05:44:00
Directory: updates              06/12/21        23:15:00

No mirror operator should have any problem figuring out how to keep
particular subtrees instead of everything.

> I don't see why the
> mirrors shouldn't have the base tree and the update tree together,

My point exactly.

> but I
> don't see why they should change their setup to have them together
> either because these really originate from different servers.

Why should any mere mortal user care from what server they originate?
Users expect updates for opensuse products to originate from the same
place as the opensuse products themselves - opensuse - not from (un)open
suse.

> The proposed change introduces inconsistency.

> http://ftp.suse.com/pub/suse/
> http://ftp.opensuse.org/pub/opensuse/
> ftp://ftp.adobe.com/pub/adobe
> ftp://ftp.redhat.com/pub/redhat

> Do you see the pattern?

Yes. My bookmarks, hotlist and favorites databases all require twice as
many entries each for SUSE instead of one as with sensible distros.

>> There should be no way to choose to update with a GUI tool and not be
>> shown everything that is available, except by explicit choice to show
>> less than everything. People are going to see the short list object,
>> choose it, and think everything is all up to date, just like I did last
>> night.

> Who made up this specification? Right now it's the other way round. You
> won't be able to get this into YOU. You're expecting YOU to do something
> it never claimed to do.

> Updating any sort of packages other than those that belong to a patch is
> explicitly unsupported.

> All security updates from SUSE are part of a patch; if YOU doesn't show
> anything, they are all installed.

Patch, smatch. All a normal user cares about is getting broken stuff
fixed, not the semantics of making updaters do their job or the names of
the files they use to do their jobs. If the title of the app says Online
Update (as YaST calls it), I expect update to mean update, not partial
update, unless the first thing it does is tell me I'm probably in the
wrong place if I want more than a subset of available updates, or unless
in YaST right beside "Online Update" is some clearly distinguishable
alternative that does offer a complete update. If my meaning escapes
you, try Ubuntu's apt-get upgrade, or Mandriva's urpmi --auto-update.

> (And yes, the functionality to update all packages to their most recent
> versions is really there. Just look for it.)

Look for it where? In YaST Online Update? If it's there somewhere, it
isn't unambiguously described.
-- 
"Let your conversation be always full of grace." Colossians 4:6 NIV

 Team OS/2 ** Reg. Linux User #211409

Felix Miata  ***  http://mrmazda.no-ip.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to