On Fri, Nov 14, 2003, F. Even wrote: > On 11/14/03 2:02 AM, "Ralf S. Engelschall" <[EMAIL PROTECTED]> wrote: > > > On Thu, Nov 13, 2003, F. Even wrote: > > > > Sorry that our documentation still lacks those details. [...] > > Is there anything I can do while using 1.3? > It is a common practice to use a release version of OpenPKG for most of the packages and make an exception to use CURRENT packages where later vendor apps are needed.
It is possible to mix and match OpenPKG branches up to a point where they become incompatible. The reason we do not promote this loudly is that it is very hard to describe the point of incompatiblity in a general fashion. Some of the critical points are macros being used in the spec files which need to be supplied by the bootstrap, same for shell functions in the rc files. Regarding spec macros and rc functions the situation is that openpkg-1.3.1-1.3.1 was upgraded to supply those introduced post-1.3.0 which are used in CURRENT (as of today :-) and probably in openpkg-2.0.0 when it becomes available. In the history of OpenPKG this is a unique issue of forward compatiblity. The more general approach is to stay with the release packages and upgrade the bootstrap to CURRENT where the bootstrap's age is somewhere between the release of the packages and the next release or CURRENT is next doesn't exist yet. OpenPKG bootstrap is always backward compatible with it's predecessor. Sometimes even with older ancestors, but no warranty. I'm talking about source compatiblity here. It is possible - and between OpenPKG 1.3 and 2.0 (aka CURRENT as of today) very likely - that binary packages are incompatible. You might need rebuilding and existing application from source in case you'll want to reinstall it. Another critical point are features in the fsl config require a later release of fsl, too. Because OSSP fsl development is driven by OpenPKG it is currently the only package where we introduce vendor updates in OpenPKG STABLE and SOLID branches, so you are safe with the latest UPD. You'll know when you need updating fsl when any UPD package requires so - build/install will tell you. In short, upgrade bootstrap to openpkg-1.3.1-1.3.1 and use postfix-2.0.16-20031028 or later. You must convince a RELEASE rpm to accept CURRENT package by adding --nodeps to the building and installation command lines. > Are there any instructions for > creating a virtual RPM with 1.3? > Only the FAQ [1]. The wholly magic is "Provides: MTA" > ...or will the import package work on 1.3? > Untested, but it should. If it doesn't, tell me and i'll fix. [1] http://www.openpkg.org/faq.html#package-type -- [EMAIL PROTECTED], Cable & Wireless ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
