Re: [pacman-dev] Versioned packages

2016-09-12 Thread Sergey Petrenko via pacman-dev
+03:00 от Jelle van der Waa ><je...@vdwaa.nl>: > >On 09/12/16 at 09:47am, Sergey Petrenko via pacman-dev wrote: >> Should I spam kernel package maintainers then, or maybe someone will resolve >> bug as wontfix? > >Not sure why they need to be spammed, you ca

Re: [pacman-dev] Versioned packages

2016-09-12 Thread Sergey Petrenko via pacman-dev
Should I spam kernel package maintainers then, or maybe someone will resolve bug as wontfix? >Суббота, 10 сентября 2016, 0:58 +03:00 от Allan McRae <al...@archlinux.org>: > >On 10/09/16 08:41, Sergey Petrenko via pacman-dev wrote: >> Here is my attempt to solve seven years

[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

[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] 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

Re: [pacman-dev] [PATCH] Option to pass packages' versions to hook. Linearize code in _alpm_hook_trigger_match_pkg.

2016-09-05 Thread Sergey Petrenko via pacman-dev
/backup-kernel#L11 manually parse package version. >Понедельник, 5 сентября 2016, 10:45 +03:00 от Allan McRae ><al...@archlinux.org>: > >On 05/09/16 03:44, Sergey Petrenko via pacman-dev wrote: >> I'm writing hooks to solve infamous kernel problem. Having version in

Re: [pacman-dev] [PATCH v2] Option to pass packages' versions to hook. Linearize code in _alpm_hook_trigger_match_pkg.

2016-09-04 Thread Sergey Petrenko via pacman-dev
gmail.com >: > >On 09/04/16 at 08:56pm, Sergey Petrenko via pacman-dev wrote: >> Variables are now at beginning of block. >> >> --- > >I would love to provide more information to hooks about the >transaction, but, without a compelling justification, I'm -1 on this

[pacman-dev] [PATCH v2] Option to pass packages' versions to hook. Linearize code in _alpm_hook_trigger_match_pkg.

2016-09-04 Thread Sergey Petrenko via pacman-dev
Variables are now at beginning of block. --- lib/libalpm/hook.c| 104 +- test/pacman/tests/TESTS | 1 + test/pacman/tests/hook-target-versions.py | 47 ++ 3 files changed, 120 insertions(+), 32 deletions(-)

Re: [pacman-dev] [PATCH] Option to pass packages' versions to hook. Linearize code in _alpm_hook_trigger_match_pkg.

2016-09-04 Thread Sergey Petrenko via pacman-dev
M +, Sergey Petrenko via pacman-dev wrote: >> --- > >Missing seems to be some rationale for this patch. What's the problem >you're interested in solving with this feature? > >> lib/libalpm/hook.c| 102 >> -- >&g

[pacman-dev] [PATCH] Option to pass packages' versions to hook. Linearize code in _alpm_hook_trigger_match_pkg.

2016-09-04 Thread Sergey Petrenko via pacman-dev
--- lib/libalpm/hook.c| 102 -- test/pacman/tests/TESTS | 1 + test/pacman/tests/hook-target-versions.py | 47 ++ 3 files changed, 118 insertions(+), 32 deletions(-) create mode 100644