Re: Rename the package command

On Thu, Aug 28, 2008 at 11:03 PM, Jan Niklas Hasse <[email protected]> wrote:
> On Thu, Aug 28, 2008 at 10:44 PM, Isak Savo <[email protected]> wrote:
>>
>> The purist in me agree with you. But the pragmatic guy on my shoulder
>> says it may not be worth it :)
>>
>> Mostly because we're solving a problem which I'm not sure exists for
>> any of our users... (please convince me otherwise)
>
> You're right, there's no user which is running into this problem
> afaik. But maybe the fix would be for reasons of precaution only.
>
> I'm also saying this, as the new stub.4.template is directly calling
> "package install <myself>" if autopackage 1.4 is installed. That's
> another reason, why I would change the name now, before 1.4.

I presume this is to solve the execute-package-directly bug, right?

How about the other stubs? Aren't there calls to 'package' inside the
other stubs?  Or in the included code in existing packages. How will
existing packages cope with renaming the 'package' command?

We *don't* want to break old packages.

> What do you think of 'apkg'? If that name is okay, I can commit a
> patch tomorrow.

I think "autopackage" is a better name. It is, after all, our "main
executable" and it seems fair to name it after the project.

It's a bit longer to write though... :-/

I'd say hold on to that patch for a while so that we can think this
one through. Is there a ticket open for this issue?

-Isak

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