Thomas,
Thanks for your quick reply. I suspected this was the case, but I just
wanted to check.
The larger concern is this: I use openpkg because it saves time (amongst
other benefits) when it comes to compiling software. If I have to upgrade
my openpkg installs just because I want to update a single package, it
adds complexity/instability to our environment.
I'm happy that openpkg is evolving (congrats on the 1.3 release !), and I
fully expect some incompatibilities with each new release, but there is
significant value for an end user such as myself being able to focus on
the software packages themselves and have a management layer (openpkg) as
transparent as possible. Not an easy thing to do, but I hope you will keep
that in mind, as I suspect you already do.
Thanks,
--
Vinod
On Mon, 4 Aug 2003, Thomas Lotterer wrote:
> Vinod!
> The %{l_value ...} macro is new to OpenPKG v1.3. Many packages use it
> and none of them can work with a v1.2 bootstrap. Other incompatiblities
> would have caught you later, like the new "-o" option in rc's %status
> section which also first appeared in OpenPKG v1.3. So you have to
> upgrade the bootstrap to OpenPKG v1.3 first, please. This shouldn't
> cause other problems as we tried to make the bootstrap backwards
> compatible. But we cannot guarantee. Using rc for starting and stopping
> daemons might give little different output and return codes which could
> become relevant if you parse the output programmatically, otherwise it's
> look'n'feel only. Good luck!
>
> PS: don't forget to have a look at the
> http://cvs.openpkg.org/openpkg-re/upgrade.txt file first.
>
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
