Package Details: lego v3.8.0-1

Git Clone URL: https://aur.archlinux.org/lego.git (read-only, click to copy)
Package Base: lego
Description: Lets Encrypt client and ACME library written in Go
Upstream URL: https://go-acme.github.io/lego/
Keywords: acme lego letsencrypt
Licenses: MIT
Conflicts: lego-bin, lego-git
Provides: lego
Submitter: ldez
Maintainer: ldez
Last Packager: ldez
Votes: 5
Popularity: 0.066121
First Submitted: 2019-01-05 05:32
Last Updated: 2020-07-02 18:48

Dependencies (2)

Required by (0)

Sources (1)

Pinned Comments

ldez commented on 2020-05-15 16:55

Since 2020-05-19, this package is built from the GitHub's sources tarball related to a release.

The binary version: https://aur.archlinux.org/packages/lego-bin/

The "git" version: https://aur.archlinux.org/packages/lego-git/

Latest Comments

1 2 Next › Last »

ldez commented on 2020-05-15 16:55

Since 2020-05-19, this package is built from the GitHub's sources tarball related to a release.

The binary version: https://aur.archlinux.org/packages/lego-bin/

The "git" version: https://aur.archlinux.org/packages/lego-git/

ldez commented on 2020-05-15 14:47

I rather doubt that the average user installing this package did so specifically because they wanted the -bin version

I don't think so. I think that you forgot all users that use non "pure-ARCH" distrib.

This is the AUR and if users aren't looking at PKGBUILDs, that's on them.

I'm not sure to share this point of view.

Personally I don't read the PKGBUILD of all the packages that I use because I don't need: I trust the user community.

You can judge me and think that I'm not an "real", "pure" arch user, it's your right, but I'm sure that I'm not alone.


But I heard your requests, so I created https://aur.archlinux.org/packages/lego-bin/

For now I don't know what will be the next step, I'm still need to think about it.

eschwartz commented on 2020-05-14 18:54

I rather doubt that the average user installing this package did so specifically because they wanted the -bin version.

grawlinson commented on 2020-05-14 08:04

This is the AUR and if users aren't looking at PKGBUILDs, that's on them.

What can be done is:

  • update lego package to compile from source
  • create lego-bin using the current PKGBUILD
  • pin a message on this package (lego) describing the changes

ldez commented on 2020-05-14 07:37

lego-bin needs to replace lego and lego need to replace lego-git but the directive replaces don't allow this case.

As I also don't want to break current user installation, maybe I can create lego-bin.

So for now, I don't have a real solution.

grawlinson commented on 2020-05-12 02:14

Ideally, this should be the PKGBUILD for the lego-bin package, and this should be the PKGBUILD for the lego package.

Are you able to create lego-bin and update the PKGBUILDs for both packages?

grawlinson commented on 2019-10-14 19:35

Found a reference here, quoting for brevity:

Packages that use prebuilt deliverables, when the sources are available, must use the -bin suffix. An exception to this is with Java. The AUR should not contain the binary tarball created by makepkg, nor should it contain the filelist.

Seems like lego-bin would be preferable.

haawda commented on 2019-10-12 11:27

There is no official documentation about this, but it is common sense to name a package -bin if it is not built from sources but sources are available. So grawlinson is right here.

ldez commented on 2019-09-01 14:21

Historically, the package lego-git manage the build from sources, and it was not created by the lego team.

This package (lego) has been created, by the lego team, to provide lego from binaries build by the lego team.

I am not able to find any official guidelines regarding the link between the name of the package and how is it built.

If anyone can give a link to an official document on the subject I am interested.

grawlinson commented on 2019-08-08 05:16

Since this does not compile source, should the package be renamed to lego-bin?