Re: Rename the package command

>> Is this by design or a bug?
>
> I don't know exactly, but I "fixed" it in 1.4.

It was by design, however the rationale behind it no longer applies.

In the early days, the idea was that the "package" command would
become a simple abstraction around rpm/dpkg/etc as well as
autopackage, so you could use one command for everything, and it'd
simplify things for the end user. Obviously that never happened and
the overly generic name just caused problems.

The reasoning behind asking you to run it directly was to allow for
blacklisting/virus scanning some future hypothetical version of the
system. By training users to run "package install foo" instead of
"./foo" you get a chance to intervene. As the installer-as-program
thing was only ever about first-time convenience anyway that made
sense. However I'd hope that most users wouldn't be using the command
line anyway in this hypothetical future world in which Linux is
popular enough to have viruses :)

---------------------------------------------------------------------
To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected]
For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]