> I agree 100% with that naming scheme, but it does have the annoying
> sideeffect that upgradepkg can't detect what package to use for an
> upgrade as they have different names (either version number or build nr).
> It would be nice if 'upgradepkg' could be given the name of the /new/
> package and then, if a package by the same name (disregarding version and
> build number) was installed, automagically would upgrade the installed
> package with the one specified. As it is now you are forced to use the
> long syntax of 'upgradepkg oldpackagename%newpackagename'.
We've kicked around a few ideas for making changes to upgradepkg to suit
the long package names. But none of them were really satisfactory. I
agree that it's a pain to have to type in the whole old package and new
package names for everything.
We could probably hash something out with clever use of cut. For now
though, I don't believe there are going to be any real changes to
upgradepkg. That kind of stuff is pretty much all left up to Patrick.
--
Chris Lumens - chris@slackware.com - KG6CIH
@n=(-42,-85,-83,-19,65,2,-10,-10,-15,-3,2,-10,73,-4,8,-4,2,79,8,17,15,7,14,2);
print map{chr(-$n[$i++]+ord)} sort(split(//,'place random string here')),"\n";
This archive was generated by hypermail 2b30 : Fri May 09 2003 - 10:00:02 PDT