Renaming package to -dev, -devel or.. ?

beta990 · 2015-10-17 10:37:30

At the moment I'm only maintaining one package in AUR (*manager-accounting: https://aur.archlinux.org/packages/manager-accounting), but I have some questions about renaming a PKG and package-managers.

The PKG installs the latest available version, so a package-manager (pacaur, yaourt, etc.) should upgrade this package when using the --devel option.
There is no git or other repo available, so I cannot append the -git flag to the pkgname as example.
Should I append -dev, -devel, -latest or something else instead? What would work best for most package-managers?

From what I understand, it's just deleting the current package and create a new package, instead of asking for renaming?

Thanks and please let me know if more info is needed.

Last edited by beta990 (2015-10-17 10:38:09)

Trilby · 2015-10-17 11:38:02

That is an odd one. I have no idea what logic pacaur and yaourt uses for their --devel flag. Those are tools that were made to use the AUR, the AUR is not made to be used by them. Makepkg has no --devel flag.

But if you wanted to use a -dev postfix on the package name, that'd make sense to me, and could be useful for users of some of those tools.

Could you also be sure to include the license in the new package as it doesn't seem to be currently included. I'm trying to confirm this now, but I'm getting around a 10bps download from the upstream source - so even though it's a tiny zip file, this could take a while. (edit: congirmed, the current package does not contain the EULA).

Spyhawk · 2015-10-17 12:31:37

This seems to be a regular package, with versioned (albeit frequent) releases. There isn't really a reason to rename this package to -dev or something else imho, you should just update the version number when needed. VCS extension (-git, -svn, -hg, -bzr and -darcs) are reserved for packages that pull the source directly from the development repository. Also, some nightly built packages use the "-nightly" extension, but here I don't think this could apply to manager-accounting either.

Moreover, there isn't a clear policy for the --devel option of AUR helpers (since these are unofficial and unsupported), but this option is usually used when there isn't a clear version number. The --devel option thus behaves differently among helpers (fe, pacaur supports the "-nighlty" extension but I don't think yaourt and packer implement it).

Last edited by Spyhawk (2015-10-17 12:31:53)

beta990 · 2015-10-17 13:01:32

Trilby wrote:

That is an odd one. I have no idea what logic pacaur and yaourt uses for their --devel flag. Those are tools that were made to use the AUR, the AUR is not made to be used by them. Makepkg has no --devel flag.
But if you wanted to use a -dev postfix on the package name, that'd make sense to me, and could be useful for users of some of those tools.
Could you also be sure to include the license in the new package as it doesn't seem to be currently included. I'm trying to confirm this now, but I'm getting around a 10bps download from the upstream source - so even though it's a tiny zip file, this could take a while. (edit: congirmed, the current package does not contain the EULA).

The --devel flag (when using pacaur, yaourt, etc.) updates packages that have a -git, -svn, -bzr, etc. flag.
But I'm not sure if it also (force) updates packages with a -devel, -dev, -latest, -nightly at the end.

There is no license file, will check the source tar, but if this is required, I will try to contact the staff/maintainers.

Spyhawk wrote:

This seems to be a regular package, with versioned (albeit frequent) releases. There isn't really a reason to rename this package to -dev or something else imho, you should just update the version number when needed. VCS extension (-git, -svn, -hg, -bzr and -darcs) are reserved for packages that pull the source directly from the development repository. Also, some nightly built packages use the "-nightly" extension, but here I don't think this could apply to manager-accounting either.
Moreover, there isn't a clear policy for the --devel option of AUR helpers (since these are unofficial and unsupported), but this option is usually used when there isn't a clear version number. The --devel option thus behaves differently among helpers (fe, pacaur supports the "-nighlty" extension but I don't think yaourt and packer implement it).

It isn't a regular package, you could compare firefox-nighly with this package. It updates the package when a new version is available (by downloading the latest version.txt).
I don't know for sure if nightly is applied for this software, since we don't know what (release) channel is used.
It's not beta, but it could be the stable repo.

I'm thinking of just adding -latest, -dev, -devel, but don't know what package-manager support these flag(s).
Is there a documentation/wiki/man to check?

Scimmia · 2015-10-17 13:19:27

You are going to be updating it on every release, right? If so, updating with the --devel option isn't really needed.

beta990 · 2015-10-17 14:13:56

Scimmia wrote:

You are going to be updating it on every release, right? If so, updating with the --devel option isn't really needed.

No, it updates automatically, everytime your install the package, it checks and updates when needed to the latest version.

Scimmia · 2015-10-17 14:23:18

It's a release package and should be treated as such.

Spyhawk · 2015-10-17 14:42:49

Scimmia wrote:

It's a release package and should be treated as such.

Correct, the -dev, -nightly suffixes don't apply here.

Trilby · 2015-10-17 23:22:26

beta990 wrote:

There is no license file, will check the source tar, but if this is required, I will try to contact the staff/maintainers.

What? It's very clearly highlighted right below the download link - and it is a hyperlink to the license:
http://www.manager.io/desktop/eula

beta990 · 2015-10-21 08:47:00

Trilby wrote:

beta990 wrote:
There is no license file, will check the source tar, but if this is required, I will try to contact the staff/maintainers.
What? It's very clearly highlighted right below the download link - and it is a hyperlink to the license:
http://www.manager.io/desktop/eula

Done! Thanks.

Arch Linux

#1 2015-10-17 10:37:30

Renaming package to -dev, -devel or.. ?

#2 2015-10-17 11:38:02

Re: Renaming package to -dev, -devel or.. ?

#3 2015-10-17 12:31:37

Re: Renaming package to -dev, -devel or.. ?

#4 2015-10-17 13:01:32

Re: Renaming package to -dev, -devel or.. ?

#5 2015-10-17 13:19:27

Re: Renaming package to -dev, -devel or.. ?

#6 2015-10-17 14:13:56

Re: Renaming package to -dev, -devel or.. ?

#7 2015-10-17 14:23:18

Re: Renaming package to -dev, -devel or.. ?

#8 2015-10-17 14:42:49

Re: Renaming package to -dev, -devel or.. ?

#9 2015-10-17 23:22:26

Re: Renaming package to -dev, -devel or.. ?

#10 2015-10-21 08:47:00

Re: Renaming package to -dev, -devel or.. ?

Board footer