On Sat, 5 Aug 2000, Ingo Luetkebohle wrote:
> On Sat, Aug 05, 2000 at 07:30:34AM +0800, John Summerfield wrote:
> > mkkickstart is for cloning the same release; it does not cope well with
> > upgrades where packages get renamed, split up differently or otherwise
> > reoganised.
>
> Exactly. Thats what rpm is for.
>
> IMHO, implementing much more flexible rules for "requires", "obsoletes" and
> the like is needed. Compare RPMs current mechanism to DEB-statements like:
> Package: samba-common
> Depends: some-package (>= 1.2.3) || some-other-package (>= 4.5.6)
> Replaces: samba
All of this is possible with current versions of RPM.
See e.g. Requires:, Obsoletes:, BuildPreReq: etc. fields.
The problem here is that you should be able to know _before_ downloading
xxxx megabytes of RPM's which packages you _do_ need for upgrade. And
which packages, while not in fact Required, _should_ be obtained and
installed (an example: if you had lpr packages, upgrading to latest beta
should probably replace it with LPRng).
One way to solve this would be to use a small(ish) upgrade package, which
would contain the relevant information. Also, the standard anaconda
installer could be extended to work in multiuser mode.
You should be able to compare an upgraded and installed system and
honestly be able to say they have the same packages installed,
configurations are similar etc.
--
Pekka Savola "Tell me of difficulties surmounted,
[EMAIL PROTECTED] not those you stumble over and fall"
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
