Package Details: pacdef 1.6.0-1

Git Clone URL: https://aur.archlinux.org/pacdef.git (read-only, click to copy)
Package Base: pacdef
Description: multi-backend declarative package manager for Linux
Upstream URL: https://github.com/steven-omaha/pacdef
Licenses: GPL3
Submitter: solnce
Maintainer: solnce
Last Packager: solnce
Votes: 6
Popularity: 0.006322
First Submitted: 2021-01-22 13:14 (UTC)
Last Updated: 2024-04-13 10:11 (UTC)

Required by (0)

Sources (1)

Latest Comments

solnce commented on 2024-11-30 20:44 (UTC)

@tvandermolen

The deletion request may seem appropriate, but is currently premature. A sudden influx of pressing RL issues has been preventing me from tending to pacdef. That's unlikely to change in the foreseeable future, unfortunately.

Nevertheless, pacdef should be installable with a frozen lock file. Therefore IMO deletion is not warranted.

But I'm quite happy that someone forked this project to keep it going. Best of luck to the new maintainers.

tvandermolen commented on 2024-11-30 20:37 (UTC)

This project seems to be abandoned. There has been no GitHub activity from the dev since May, and no response to 2-month old Issue #90 about an outdated dependency, which chrpinedo mentioned here.

Some others forked this and created metapac, which is also on AUR.

chrpinedo commented on 2024-10-17 20:16 (UTC)

I have this error...

   Compiling indexmap v2.2.6
error: failed to run custom build command for `alpm v3.0.5`

Caused by:
  process didn't exit successfully: `/home/zako/.cache/yay/pacdef/src/pacdef-1.6.0/target/release/build/alpm-3198e09dd8f1f138/build-script-build` (exit status: 101)
  --- stderr
  thread 'main' panicked at /home/zako/.cargo/registry/src/index.crates.io-6f17d22bba15001f/alpm-3.0.5/build.rs:25:13:
  this version of alpm.rs does not support libalpm v15.0.0 only v14.x.x is supported
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
==> ERROR: A failure occurred in build().
    Aborting...
 -> error compilando: pacdef-exit status 4
 -> Ha fallado al instalar los siguientes paquetes. Una intervención manual es requerida:
pacdef - exit status 4

solnce commented on 2024-01-30 11:49 (UTC) (edited on 2024-01-30 11:49 (UTC) by solnce)

@mwaddoups see https://wiki.archlinux.org/title/Makepkg#Usage

pkgconf is provided by base-devel

mwaddoups commented on 2024-01-29 22:56 (UTC)

I think this package has a dependency (may just be build) on pkg-config?

I got a build error below

--- stderr
  thread 'main' panicked at /home/<username>/.cargo/registry/src/index.crates.io-6f17d22bba15001f/alpm-sys-2.1.3/build.rs:26:10:
  called `Result::unwrap()` on an `Err` value: Could not run `PKG_CONFIG_ALLOW_SYSTEM_LIBS=1 PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 pkg-config --libs --cflags libalpm libalpm >= 13.0.0`
  The pkg-config command could not be found.

  Most likely, you need to install a pkg-config package for your OS.
  Try `apt install pkg-config`, or `yum install pkg-config`,
  or `pkg install pkg-config`, or `apk add pkgconfig` depending on your distribution.

  If you've already installed it, ensure the pkg-config command is one of the
  directories in the PATH environment variable.

This was resolved by installing pkgconf.

MaximGun commented on 2023-06-01 13:45 (UTC)

This builds fine on aarch64. Worth updating the PKGBUILD.

solnce commented on 2022-08-27 15:40 (UTC)

Yes, I did it a couple of times.

lmbbrkr commented on 2022-08-27 15:33 (UTC)

Have you tried running it a second time? pip caches stuff in ~/.cache/pip (which you likely already had in your "normal" $HOME from previous build). First run will be slower regardless.

solnce commented on 2022-08-26 20:13 (UTC)

Thanks for your input! I wasn't aware of that option. I tried it, and it leads to increased build times for me (from 7 to 10 seconds), therefore I am not going to apply that.

If it's possible to achieve the same thing without the increase in build time, please let me know.

lmbbrkr commented on 2022-08-26 19:21 (UTC)

Probably a good idea to use HOME=/tmp pip install ... so pip doesn't read user's pip.conf, as having user = yes results it installing in ~/.local.