Search Criteria
Package Details: ledger-live 2.79.1-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/ledger-live.git (read-only, click to copy) |
---|---|
Package Base: | ledger-live |
Description: | Maintain your Ledger devices |
Upstream URL: | https://github.com/LedgerHQ/ledger-live |
Keywords: | bitcoin cryptocurrency wallet |
Licenses: | MIT |
Submitter: | meriadec |
Maintainer: | phnx47 |
Last Packager: | phnx47 |
Votes: | 19 |
Popularity: | 0.063011 |
First Submitted: | 2018-07-19 09:01 (UTC) |
Last Updated: | 2024-04-25 08:32 (UTC) |
Dependencies (5)
- electron28 (electron28-binAUR)
- ledger-udevAUR (ledger-udev-gitAUR)
- node-gyp (corepackerAUR) (make)
- nvmAUR (nvm-gitAUR) (make)
- pnpm (corepackerAUR, yarn-pnpm-corepackAUR) (make)
Required by (2)
- vechain-sync-bin (optional)
- vechain-sync2-bin (optional)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 12 Next › Last »
ivanmlerner commented on 2023-01-30 22:44 (UTC)
Source checksum is not matching.
phnx47 commented on 2023-01-29 09:52 (UTC) (edited on 2023-01-29 10:08 (UTC) by phnx47)
LedgerHQ fixed bug: Error when building from release archive without git repo (#1719). This package build from release archive again!
phnx47 commented on 2022-12-10 02:23 (UTC) (edited on 2022-12-10 02:34 (UTC) by phnx47)
@intelfx Fixed git folder.
About
_check_git_rev
, if I specify commit to build - it makes possible build reverted release: e0e5bb6ac602e121d3b02494323ddbe680e13bf7. I don't want install reverted released. I started worry about 'force push' in future. I added_check_git_rev
function to protect from 'force push'. I want manually check 'force push' or 'delete' tag cases.Thanks!
phnx47 commented on 2022-12-10 02:17 (UTC)
@HD_hirku I added comment to git log
HD_hirku commented on 2022-12-09 20:23 (UTC)
You should have put your pinned comment message https://aur.archlinux.org/packages/ledger-live#comment-893072 into the git log for 1b63bdcdc18c. Otherwise it looks like stupid nonsense.
Shame on Ledger.
intelfx commented on 2022-12-09 19:35 (UTC) (edited on 2022-12-09 19:41 (UTC) by intelfx)
Why are you doing this? You are causing a completely new git repository to be cloned with each new release, especially making life miserable for people with shared
$SRCDEST
. The whole point of git is to not have to do that, so please don't.The
_check_git_rev
dance also seems useless. Either specify a#commit=<output of git rev-parse <tag>^0>
instead of#tag=<tag>
, or don't.phnx47 commented on 2022-12-09 16:01 (UTC) (edited on 2022-12-09 17:21 (UTC) by phnx47)
Build temporary fails for v2.51.0!
I updated to v2.51.0 but LedgerHQ reverted release and deleted tag.
You should manually set
pkgver=2.50.1
and set_gitrev=c5aba7d153e07729c478b159a895f3bc51d89e1d
, can check git hash with command:git rev-parse @ledgerhq/live-desktop@2.50.1
sudoforge commented on 2022-11-30 16:44 (UTC) (edited on 2022-11-30 16:47 (UTC) by sudoforge)
@phnx47 that assumes people aren't building in a chroot, which is really what they should be doing with AUR packages.
I think the statement that "
fnm
is better thannvm
" is a little contrived and subjective; I don't use JS with any sort of regularity (SRE; primarily golang and rust), but some cursory searching doesn't indicate thatfnm
has supplantednvm
as "the default".That said, this is your package. You do with it what you want, and have no need to make adjustments to it unless you think it is logical and needed.
Note, however, that it is typically recommended to read and follow the packaging guidelines for packages you want to maintain. For this, we have the NodeJS Package Guidelines. These are not rules, simply guidelines.
phnx47 commented on 2022-11-21 01:53 (UTC) (edited on 2022-11-21 01:55 (UTC) by phnx47)
I tried to improve build with
fnm
, but this create a lot of discussions. Let's explain again.To build
ledger-live
you need exactly NodeJS 16: https://github.com/LedgerHQ/ledger-live/tree/%40ledgerhq/live-desktop%402.49.2/apps/ledger-live-desktop#requirements.I can just pin
nodejs-lts-gallium
, many packages do same thing, for examplecode
: https://github.com/archlinux/svntogit-community/blob/packages/code/trunk/PKGBUILD. It is ok for Arch Packages, but for AUR create nodejs versions conflicts with every upgrade packages. Checkvscodium
: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=vscodium. There isnvm
dependency. It makes possible build package without nodejs versions conflicts.fnm
is better alternative fornvm
. One morecode-git
: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=code-git, there isnodejs-lts-fermium
, they forgot to update nodejs version and build failes!« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 12 Next › Last »