Re: [pacman-dev] [PATCH v8 01/12] bacman: allow for multiple packages as arguments

2016-09-09 Thread Allan McRae
On 05/09/16 03:37, Gordian Edenhofer wrote: > On Sun, 2016-09-04 at 11:21 -0500, Doug Newgard wrote: >> On Sun, 4 Sep 2016 18:13:56 +0200 >> Gordian Edenhofer wrote: >> >>> >>> To enable the creation of multiple packages with one command move >>> the >>> assembly

[pacman-dev] Versioned packages

2016-09-09 Thread Sergey Petrenko via pacman-dev
Here is my attempt to solve seven years old infamous problem: https://bugs.archlinux.org/task/16702 Patch won't solve problem out of the box, a small changes in kernel PKGBUILD will be required, but only concerning install part. Idea behind patch is pretty simple: 1) Configure list of packages

[pacman-dev] [PATCH 1/2] Tests for expected behavior of archiving mechanism. Edits to testing framework required for handling multiple versions of package.

2016-09-09 Thread Sergey Petrenko via pacman-dev
Unfortunately, some changes are required to testing framework to handle multiple versions of package. New tests should make expected behavior of `archived` packages pretty clear. --- test/pacman/pmdb.py | 51 +++- test/pacman/pmpkg.py

[pacman-dev] [PATCH 2/2] Ability to keep several old versions of package when they have no file conflicts with new version.

2016-09-09 Thread Sergey Petrenko via pacman-dev
I had gave a big thought to the question, who should decide whether to try to archive package. At first glance it looks like maintainer's responsibility. She/he/it creates a package without file conflicts intending possibility for multiple versions to be installed on a system. Yet this means

Re: [pacman-dev] Versioned packages

2016-09-09 Thread Allan McRae
On 10/09/16 08:41, Sergey Petrenko via pacman-dev wrote: > Here is my attempt to solve seven years old infamous problem: > https://bugs.archlinux.org/task/16702 > > Patch won't solve problem out of the box, a small changes in kernel PKGBUILD > will be required, but only concerning install part. >