ow
down the process.
I really wanted to suggest a patch but I didn't find a easy way
(understand a small patch) to fix it and I would like your opinion on
point 1) first.
Regards,
Guillaume.
onal), all next servers will be tried and all will give the same
error.
I really wanted to suggest a patch but I didn't find a easy way
(understand a small patch) to fix it and I would like your opinion on
point 1) first.
Regards,
Guillaume.
Le 25/08/2015 23:34, Dave Reisner a écrit :
On Tue, Aug 25, 2015 at 09:21:50PM +0200, Guillaume wrote:
To not block the GUI, I run trans_commit function in a g_thread and I can't use SIGINT signal. I have
no way to correctly stop curl process. I propose to look for a particular value to
04 AM, "Guillaume Benoit" wrote:
>
> Hi,
> working on a GUI frontend for libalpm, I noticed that download process
lakes for an internal interrupt mechanism. Download cancellation is only
handled by catching SIGINT signal.
> I think it would be a benefit for libalpm to
Hi,
working on a GUI frontend for libalpm, I noticed that download process
lakes for an internal interrupt mechanism. Download cancellation is only
handled by catching SIGINT signal.
I think it would be a benefit for libalpm to have more correct download
interrupt mechanism like trans_interrupt
es, the one for explicit packages, and the other for
dependencies, examples:
$ pacman -S epiphany
[sudo] password for guillaume:
resolving dependencies...
looking for conflicting packages...
Package (1) New Version Net Change Download Size
extra/epiphany 3.12.0-1 6.89 MiB 1.48 MiB
When verbose package is activated, the table is displayed two times,
once for explicit packages and a second time for dependencies.
This helps understanding the upgrade process. You can focus on on
explicit package and gives less attention to dependencies.
Design choices:
-- If a table does not
ill not really explicit for users.
I'll wait for a few other feedbacks and I'll update the patch to add
an asterix after the package name.
--
Guillaume
--
?
(I had never though a *so simple* hack would generate so much discussion ;)
--
Guillaume
> Of the two options, I would prefer the dependencies to be shown in
> grey instead of having explicitly installed packages typeset in bold.
> I don't feel too strongly about this though, so I won't complain if
> everyone else prefers bold.
There is a second option. Instead of just flaging deps OR
. grey).
Signed-off-by: Guillaume Bouchard
---
src/pacman/conf.c | 1 +
src/pacman/conf.h | 1 +
src/pacman/util.c | 13 ++---
3 files changed, 12 insertions(+), 3 deletions(-)
diff --git a/src/pacman/conf.c b/src/pacman/conf.c
index 4b7ec05..243203f 100644
--- a/src/pacman/conf.c
+++ b
ting in bold the name of explicitly
installed packages. This patch put in grey the name of "dependencies".
Which one should we keep ?
--
Guillaume
Any feedbacks on that patch ? Must I change something ?
On Fri, Jan 24, 2014 at 5:22 PM, Guillaume Bouchard
wrote:
> In extended table view, packages which are not explicitly installed are
> displayed in grey. This helps understanding why
> packages are updated.
>
> This he
On Fri, Jan 24, 2014 at 4:24 PM, Jerome Leclanche wrote:
> On Fri, Jan 24, 2014 at 2:17 PM, Guillaume Bouchard
> wrote:
>> In extended table view, packages which are explicitly installed are
>> displayed as CELL_TITLE (i.e. in bold). This helps understanding why
>&
. grey).
Signed-off-by: Guillaume Bouchard
---
src/pacman/conf.c | 1 +
src/pacman/conf.h | 1 +
src/pacman/util.c | 13 ++---
3 files changed, 12 insertions(+), 3 deletions(-)
diff --git a/src/pacman/conf.c b/src/pacman/conf.c
index 5450f3b..785061b 100644
--- a/src/pacman/conf.c
+++ b
remove the explicit packages which are not longer required. During
remove, it shows all the explicit packages which are also removed by a
cascade removal. During install, it provides a feedback on how your
action will affect the database.
Signed-off-by: Guillaume Bouchard
---
src/pacman/util.c | 7
Hello.
A really small change in pacman which, I hope, improves the feedback
about explicit packages on install/removal/update.
Have a nice day.
Output of git format-patch origin:
>From bd5c3aa7826c3c073cca691f0e30b5363487cd6f Mon Sep 17 00:00:00 2001
From: Guillaume Bouchard
Date: Fri, 24
OK so hopefully this one will work nicely...
=== PATCH ===
diff --git a/doc/.gitignore b/doc/.gitignore
index f047aaa..aebf7a0 100644
--- a/doc/.gitignore
+++ b/doc/.gitignore
@@ -3,6 +3,7 @@ libalpm.3
makepkg.8
makepkg.conf.5
pacman.8
+pacman-key.8
pacman.conf.5
repo-add.8
repo-remove.8
dif
On 20 September 2010 14:06, Guillaume ALAUX wrote:
> On 20 September 2010 13:58, Allan McRae wrote:
>> Hi,
>>
>> FYI, it is much easier to comment (and separate comments from the patch) if
>> things are posted inline. Here goes some brief comments in cut paste sort
stdb in GnuPG
>
>
> Allan
Hello,
> it is much easier to comment if things are posted inline
OK I hadn't think about it !
> Make these small adjustments it is basically good to go
They also look OK to me, I will change that.
> Even better if you submit as a patch with the necessary autotools changes
Will try to :)
--
Guillaume
On 18 September 2010 23:40, Guillaume ALAUX wrote:
> On 18 September 2010 22:05, Guillaume ALAUX wrote:
>> On 16 September 2010 17:58, Denis A. Altoé Falqueto
>> wrote:
>>> On Thu, Sep 16, 2010 at 4:37 AM, Guillaume ALAUX
>>> wrote:
>>>> Hi Denis,
On 18 September 2010 22:05, Guillaume ALAUX wrote:
> On 16 September 2010 17:58, Denis A. Altoé Falqueto
> wrote:
>> On Thu, Sep 16, 2010 at 4:37 AM, Guillaume ALAUX
>> wrote:
>>> Hi Denis, Hi everyone,
>>>
>>> I'm really pleased to see you
On 16 September 2010 17:58, Denis A. Altoé Falqueto
wrote:
> On Thu, Sep 16, 2010 at 4:37 AM, Guillaume ALAUX
> wrote:
>> Hi Denis, Hi everyone,
>>
>> I'm really pleased to see you're back on track.
>
> Hi and thanks for the support :)
>
>>> I
;;
> + -f|--finger)
> + ${GPG_PACMAN} --batch --fingerprint $*
> + ;;
> + -e|--export)
> + if (( $# == 0 )); then
> + ${GPG_PACMAN} --armor --export
> + else
> + while (( $# > 0 )); do
> + ${GPG_PACMAN} --armor --export "$1"
> + shift
> + done
> + fi
> + ;;
> + -r|--receive)
> + if (( $# < 2 )); then
> + error "$(gettext "You need to specify the keyserver
> and at least one key identifier")"
> + usage
> + exit 1
> + fi
> + keyserver="$1"
> + shift
> + ${GPG_PACMAN} --keyserver "${keyserver}" --recv-keys $*
> + ;;
> + -t|--trust)
> + if (( $# == 0 )); then
> + error "$(gettext "You need to specify at least one
> key identifier")"
> + usage
> + exit 1
> + fi
> + while (( $# > 0 )); do
> + # Verify if the key exists in pacman's keyring
> + if ${GPG_PACMAN} --list-keys "$1" > /dev/null 2>&1;
> then
> + ${GPG_PACMAN} --edit-key "$1"
> + else
> + error "$(gettext "The key identified by %s
> doesn't exist")" "$1"
> + exit 1
> + fi
> + shift
> + done
> + ;;
> + --adv)
> + msg "$(gettext "Executing: %s ")$*" "${GPG_PACMAN}"
> + ${GPG_PACMAN} $* || ret=$?
> + exit $ret
> + ;;
> + --help)
> + usage
> + ;;
> + --version)
> + version
> + exit 0
> + ;;
> + *)
> + usage
> + exit 1
> + ;;
> +esac
> +
> --
> 1.7.2.3
>
>
>
Hi Denis, Hi everyone,
I'm really pleased to see you're back on track.
> If any of the collaborators want to help, this is the time
I would be glad to.
I see you need help to write the man right? Is this the number one
task? Because I could also help with some more technical things if
needed.
Just let me know.
--
Guillaume
24 matches
Mail list logo
