Skip to content
This repository has been archived by the owner on May 31, 2018. It is now read-only.

pacman 5.1 adjustment #726

Open
rmarquis opened this issue Jul 11, 2017 · 7 comments
Open

pacman 5.1 adjustment #726

rmarquis opened this issue Jul 11, 2017 · 7 comments

Comments

@rmarquis
Copy link
Owner

rmarquis commented Jul 11, 2017

List of required adjustments for pacman 5.1.

makepkg: do not create symlinks in build directory
Setting PKGDEST and friends enables us to keep all built packages in a single
location.  Symlinking these files into the build directory creates unnecessary
clutter and requires clean-up in multiple places when removing old version.

The removal of the symlinks make the install of VCS packages fail:

        # retrieve filename
        unset builtpkgs builtdepspkgs
        for j in "${pkgsdepslist[@]}"; do
            unset builtpkg
            [[ $aurdevelpkgsAver ]] && depsAver="$aurdevelpkgsAver" || depsAver="$(GetJson "varvar" "$json" "Version" "$j")"
            GetBuiltPkg "$j-$depsAver" "$clonedir/${basepkgs[$i]}"
            [[ " ${aurdepspkgs[@]} " =~ " $j " ]] && builtdepspkgs+=($builtpkg) || builtpkgs+=($builtpkg)
        done

See also #461, which was implemented to also remove these symlinks leftover. A revamp might be needed here.

@rmarquis rmarquis added the todo label Jul 11, 2017
@rmarquis rmarquis added this to the 5.0.x - later milestone Jul 11, 2017
@rmarquis
Copy link
Owner Author

Adjusted in 620eff5 and c8ff58f.

Only pacman 5.1 compatibility has been added in master, cleaning code still needs to be reworked.

@AladW
Copy link
Contributor

AladW commented Jul 12, 2017

Is there an ETA for the pacman 5.1 release? I don't see a mention on pacman-dev

@rmarquis
Copy link
Owner Author

No ETA yet. Since pacman 5.0.2 is quite fresh, I don't expect it before a few months.

@rmarquis rmarquis modified the milestones: 4.8.x - new features, 5.0.x - later Jul 21, 2017
@rmarquis
Copy link
Owner Author

Some conditional check needs to be uncommented in c0bc632 to ensure full pacman 5.1 compatibility.

@rmarquis
Copy link
Owner Author

You can check the change log of the pacman git repo. There is very little changes relevant to pacaur usage.

@rmarquis
Copy link
Owner Author

See also the --packagelist patch here: https://lists.archlinux.org/pipermail/pacman-dev/2017-October/022190.html (not in master yet)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants
@rmarquis @AladW and others