On Mon Nov 13, 2000 at 12:11:49PM +1100, Ron Stodden wrote:
> > development updates = cooker
> > normal updates = security/bugfix/enhancedment updates (for 7.2)
> >
> > Having the label development updates changed to cooker updates is a
> > matter of semmantics. cooker is a *developer* distribution so the
> > name is not inaccurate. Development updates does not mean tools like
> > gcc or egcs... it means cooker "development".
> No! As I said, the word 'Development' is already taken as a class of
> install (plainly intended for use by developers), therefore a
> legitimate reading of 'Development updates' is updates to a
> development install.
Since when did MandrakeUpdate become the install program? A developer
install has nothing to do with development updates.
> You would have 'Development Updates' mean 'Cooker updates'.
> 'Development updates' would therefore become ambiguous, while 'Cooker
> updates' is unambiguous. Therefore the choice of wording is also
> unambiguous <g>. 'Cooker updates' wins, no protest.
Development updates *does* mean cooker updates. And doesn't the
little warning tell you anything? I didn't think we were in the habit
of handing out untested/broken/*development* applications for every
day use for the public (except in Cooker, of course), and especially
not with security updates! You think we're going to hand out the
alpha version of bind to fix a bind security vulnerability? Come on
now... let's get realistic here!
> Remember that you can do a number of other class of install of
> Cooker, eg recommended, in which case that Cooker installation has no
> involvement with development at all.
Sure. But you don't perform those *installs* with Mandrake*Update*!!
They're two entirely different entities, completely separate.
> You are also confusing development done by or for MandrakeSoft (ie
> development of the next release, ie cooker) with development done by
> and for a Mandrake User, which end is provided for by having the
> 'developer' class of install (which does not require the use of
> cooker).
*I'm* not confusing anything, Ron... you're the one confused... =) No
one else seems to have a hard time with it, and it made perfect sense
to me when I looked at it. Again, you're talking install... Drakx
and MandrakeUpdate are not the same thing so the same terms do not
apply. MandrakeUpdate does not perform Mandrake installs, nor does
Drakx perform the same function as MandrakeUpdate (and they never
will).
> Proper semantics, correct use of words, is critically important.
Sure. But I think you read too much into it. You're comparing terms
between apples and oranges. It doesn't apply.
If you want to argue about this, however, take it up with qa. I don't
write or maintain MandrakeUpdate, so trying to convince me of this
won't change MandrakeUpdate. Honestly, however, I do not see your
point of view at all. Yes, proper semantics is one thing, but between
two completely different applications? Come on... If this is the
case, we may want to change the name of "Cooker" to something entirely
different before someone thinks it is full of kitchen/cooking
applications or something... =)
--
[EMAIL PROTECTED], OpenPGP key available on www.keyserver.net
1024D/FE6F2AFD 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD
- Danen Consulting Services www.danen.net, www.freezer-burn.org
- MandrakeSoft, Inc. www.linux-mandrake.com
Current Linux uptime: 5 days 22 hours 12 minutes.
