Package management (was Re: How-to Monticello Configuration)
J J
azreal1977 at hotmail.com
Sat Mar 10 20:53:52 UTC 2007
I may have asked this before, and if so I apologize, but is there any place
that shows the different packaging systems, what they have in common, what
is different, etc.?
I think it is important to either make these things compatible with each
other or consider adopting just one. Everyone likes choices, but for
system/environment components they can be more problem then benefit.
We don't want to do like Linux with way too many choices for things that
don't matter that much (e.g. 23412341234 different window managers) but
completely missing seemingly low hanging fruit (e.g. not a single free
installer I am aware of that can automatically set up my new Linux machine
to authenticate via LDAP they way windows does out of the box).
>From: Bert Freudenberg <bert at freudenbergs.de>
>Reply-To: The general-purpose Squeak developers
>list<squeak-dev at lists.squeakfoundation.org>
>To: The general-purpose Squeak developers
>list<squeak-dev at lists.squeakfoundation.org>
>Subject: Re: How-to Monticello Configuration
>Date: Fri, 9 Mar 2007 18:08:33 +0100
>
>On Mar 9, 2007, at 16:56 , J J wrote:
>
>> MC Configs just pick the newest of everything?
>
>There seems to be a misconception about MCConfigs here.
>
>Each MCConfiguration specifies a *fixed* set of MC versions identified by
>version name and UUID, which is loaded.
>
>*Additionally*, provided your repository organization and naming method
>follows a certain scheme, you can update the MCConfiguration automatically
>by using the highest-numbered package version found. This "updating" of
>the config does not actually install anything, it just enlists new
>versions. This configuration then can be loaded just like a manually
>constructed configuration.
>
>This automatic update function is mostly a convenience for developers,
>otherwise you always had to manually construct a configuration which is
>tedious. If you use configurations for deployment I'd suggest not to use
>the update feature but deliver a verified working config to your users.
>
>If you use a different development method or naming scheme in your project
>you can still use MCConfigs, it's just that the automatic update would not
>be usable.
>
>- Bert -
>
>
>
_________________________________________________________________
Find a local pizza place, movie theater, and more
.then map the best route!
http://maps.live.com/?icid=hmtag1&FORM=MGAC01
More information about the Squeak-dev
mailing list
|