Package Details: freecalypso-ota-tools-hg r11.b4b4a822286c-1

Git Clone URL: https://aur.archlinux.org/freecalypso-ota-tools-hg.git (read-only, click to copy)
Package Base: freecalypso-ota-tools-hg
Description: FreeCalypso tools for OTA SIM programming
Upstream URL: https://www.freecalypso.org/hg/themwi-ota-tools
Licenses: custom
Groups: freecalypso
Conflicts: freecalypso-ota-tools
Submitter: fixeria
Maintainer: fixeria
Last Packager: fixeria
Votes: 0
Popularity: 0.000000
First Submitted: 2023-08-31 20:36 (UTC)
Last Updated: 2024-05-23 11:23 (UTC)

Latest Comments

dreieck commented on 2024-05-24 11:04 (UTC)

Please add freecalypso-ota-tools to the provides and conflicts arrays.

There is currently no 'release' variant for this package, but I added conflicts anyway. Not sure about adding to provides, the package implicitly provides itself, does it?

freecalypso-ota-tools-hg provides freecalypso-ota-tools-hg as beeing itself, yes. But not freecalypso-ota-tools.

As far as the Arch Linux VCS package guidelines are concerned (and this -hg is a VCS package), the VCS package should list the "base" package in the provides and conflicts arrays, and not the other way round.

(Practical reason: One can easily depend on freecalypso-ota-tools, and it is the user's choice weather to install the base or -hg variant.)

This holds also true even if there is (at the present date) no non-VCS package around. Having the generic package in provides array allows to depend on it straight from the start!, not giving messed up dependencies later when it might come around, or when someone creates a -bin package, or so.

You need to make the license identifier SPDX-compliant: [...]

I am not sure what should I use. Looks like public domain?

Say e.g. LicenseRef-PublicDomain, and install a license file into /usr/share/licenses/${pkgname}/.

Regards!

fixeria commented on 2024-05-23 11:23 (UTC)

Hi @dreieck,

Please add freecalypso-ota-tools to the provides and conflicts arrays.

There is currently no 'release' variant for this package, but I added conflicts anyway. Not sure about adding to provides, the package implicitly provides itself, does it?

openssl needs to be added to the depends or optdepends array: [...]

Done, thanks.

Can you install (or symlink) all the executables from /opt/freecalypso/bin/ into /usr/bin/, please?

Done (see also https://www.freecalypso.org/pipermail/community/2024-May/000927.html).

You need to make the license identifier SPDX-compliant: [...]

I am not sure what should I use. Looks like public domain?

dreieck commented on 2024-04-26 21:27 (UTC)

Please add freecalypso-ota-tools to the provides and conflicts arrays.

Regards and thanks for maintaining!

dreieck commented on 2024-04-26 21:25 (UTC) (edited on 2024-04-26 21:29 (UTC) by dreieck)

openssl needs to be added to the depends or optdepends array: 

freecalypso-ota-tools-hg E: Dependency openssl detected and not included (libraries ['usr/lib/libcrypto.so.3'] needed in files ['opt/freecalypso/bin/ota-smswrap-sjs1'])

Regards!

dreieck commented on 2024-04-26 21:25 (UTC)

Can you install (or symlink) all the executables from /opt/freecalypso/bin/ into /usr/bin/, please?

Regards!

dreieck commented on 2024-04-26 21:24 (UTC)

You need to make the license identifier SPDX-compliant: 

freecalypso-ota-tools-hg E: custom is not a valid SPDX license identifier. See https://spdx.org/licenses/ for valid identifiers, or prefix the identifier with 'LicenseRef-', if it is custom.

Regards and thanks for maintaining!