Package Details: silicon 0.2.6-3

Git Clone URL: https://aur.archlinux.org/silicon.git (read-only)
Package Base: silicon
Description: Create beautiful image of your code
Upstream URL: None
Keywords: rust silicon
Licenses: MIT
Submitter: radmen
Maintainer: radmen
Last Packager: radmen
Votes: 0
Popularity: 0.000000
First Submitted: 2019-08-02 08:29
Last Updated: 2019-09-15 19:05

Latest Comments

radmen commented on 2019-09-17 07:38

@Svenstaro I'm sorry. I'm the idiot here. I've taken yet another look at the miniserve and just realized that I omitted the build() step. Apologies!

Svenstaro commented on 2019-09-16 23:44

Thanks for the changes! However, I'm very sure my miniserve PKGBUILD issues the exact same cargo call to build the package from that you're now using as well. Otherwise it'd have to be called miniserve-bin (which does exist and does what you said).

radmen commented on 2019-09-16 20:00

@Svenstaro I've looked at the PKGBUILD of miniserve. It's fetching the binary generated during Travis job thus it's using the precompiled (or should I say - prebuilt?) binary.

Re: silicon package - I've updated the PKGBUILD. It now uses the recommended --release and --locked flags. Thanks for pointing this out.

Svenstaro commented on 2019-09-16 13:39

miniserve does not use the precompiled binary but it reproducibly compiles its own binary. cargo-pkgbuild should be changed to use arch recommended practices.

radmen commented on 2019-09-15 18:43

@Svenstaro miniserve uses the precompiled binary. It's one of the ways of making AUR packages, however the preferred way IIRC is to compile them from the source code.

silicon follows the schema generated by cargo-pkgbuild. It's slightly different the proposed version from Arch wiki. I'll adjust it to the suggestions from the wiki.

Svenstaro commented on 2019-09-15 01:55

This is not the proper way to build rust packages. You could look at this [0] for some inspiration.

[0] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=miniserve