Ticket #16 (closed Defect: worksforme)

Opened 1 year ago

Last modified 2 months ago

mkapspec default to AutopackageTarget 1.0

Reported by: taj Assigned to: isak
Priority: Medium Milestone: 1.3
Component: mkapspec Version: 1.2.2
Severity: Normal Keywords:
Cc:

Description

mkapspec sets AutopackageTarget: 1.0 when creating the specfile. It probably should default to the latest Autopacakge target so packagers don't get confused (or at least 1.2 for now).

Change History

05/08/07 11:05:51 changed by isak

The reasoning was that we didn't want to impose a version requirement on autopackage 1.2 for packagers unless they actually needed the new features. (Think added installation/download time for users who already have apkg1.0 installed)

I don't know.. what do you think? What are the benefits of forcing 1.2? Do they outweight the downsides?

05/09/07 11:59:26 changed by isak

  • status changed from new to closed.
  • resolution set to wontfix.

Closing for the reasons explained in comment above

09/06/07 02:48:52 changed by isak

  • status changed from closed to reopened.
  • resolution deleted.
  • milestone set to 1.2.6.

I just remembered that with mkapspec 0.5, it can create an install script that contains API that is 1.2 only. If so, it should set autopackage target accordingly.

Reopening this ticket.

04/22/08 13:34:21 changed by Jan-Nik

Doesn't makepackage set AutopackageTarget to 1.2? http://trac.autopackage.org/browser/main/trunk/makepackage

08/01/08 20:02:18 changed by Jan-Nik

  • milestone changed from 1.2.6 to 1.3.

Milestone 1.2.6 deleted

08/02/08 07:45:47 changed by Jan-Nik

  • status changed from reopened to closed.
  • resolution set to worksforme.

I'm closing this, feel free to reopen it, if this is still an issue.