[pacman-dev] [feature request] ignore lost+found in /var/lib/pacman when running -Sc

2008-07-20 Thread solsTiCe d'Hiver
n -Sc ! a good or bad idea ? your call From 6b07694fa73499bb89556c151be39160c5ecad2a Mon Sep 17 00:00:00 2001 From: solsTiCe d'Hiver <[EMAIL PROTECTED]> Date: Sun, 20 Jul 2008 09:32:18 +0200 Subject: [PATCH] ignore lost+found directory when cleaning unsused repository directory -

[pacman-dev] [BUG] alpm_list_remove need an initalized pointer for void **data

2008-08-07 Thread solsTiCe d'Hiver
hi. i am playing with alpm and db4 to make a little program for me. just for fun. and in this new release of libalpm (along pacman 3.2.0) i have found that alpm_list_remove behave differently than before. so the last parameter (void **data) need to be initialized to avoid a seg fault. it happe

Re: [pacman-dev] [BUG] alpm_list_remove need an initalized pointer for void **data

2008-08-07 Thread solsTiCe d'Hiver
for me it is a problem with alpm_list_remove but i am not an expert. look at this #include int compare_int(const void *a, const void *b) { const int* ia = (const int *)a; const int* ib = (const int *)b; return (*ia > *ib) - (*ia < *ib); } int main(void) { alpm_list_t *l=NULL;

Re: [pacman-dev] [BUG] alpm_list_remove need an initalized pointer for void **data

2008-08-07 Thread solsTiCe d'Hiver
> Or what do we do here? Double pointers start confusing me. i reach here the limit of my knowlegde of C too. but why not : if(data) { data = NULL; } if have found by trial and error that's the only thing that is not seg faulting and void **data; data=NULL; is the same than void **data=NUL

Re: [pacman-dev] [BUG] alpm_list_remove need an initalized pointer for void **data

2008-08-08 Thread solsTiCe d'Hiver
oops my bad... ___ pacman-dev mailing list pacman-dev@archlinux.org http://archlinux.org/mailman/listinfo/pacman-dev

Re: [pacman-dev] GIT 2008 User Survey

2008-09-02 Thread solsTiCe d'Hiver
hi, i tried and give up learning git before 1.5 release. so i just learn efforts have been made to improve git and its documentation for 1.5 release. i re-tried to learn it again and find it now easier, especially with the videos i have found: http://excess.org/article/2008/07/ogre-git-tutoria

[pacman-dev] problem with deltas file generated by repo-add and what _alpm_delta_parse expects

2008-09-14 Thread solsTiCe d'Hiver
hi. i browse into alpm code, and just find that repo-add adds lines like that to a deltas file $fromver $tover $deltasize $deltafile $deltamd5 but _alpm_delta_parse (in delta.c) which is used in be_files.c, expect the same line to be $oldfile $oldmd5 $newfile $newmd5 $deltafile $deltamd5 $deltas

[pacman-dev] little translation error

2012-02-26 Thread solsTiCe d'Hiver
hi. I have sent a message about that to shining on transifex, but it seems to go unnoticed so I am reposting it here salut, j'ai noté cette petite erreur de traduction: #, c-format msgid ":: Import PGP key %s, \"%s\", created %s?" msgstr ":: Importation de la clé PGP %s, «

[pacman-dev] [PATCH] use bitwise shift operator in enum "bit field"

2009-09-26 Thread solsTiCe d'Hiver
This offers a cleaner way to deal with constant in enum and allow easy maintainance Signed-off-by: solsTiCe d'Hiver --- lib/libalpm/alpm.h | 56 ++-- lib/libalpm/db.h | 12 +- 2 files changed, 34 insertions(+), 34 deletions(-)

[pacman-dev] proof of concept code with bsd db4

2009-10-31 Thread solsTiCe d'Hiver
hi. i wanted to make a new bsd db4 back-end for alpm. but i never reached my goal. and will not all i have is a proof of concept code that use bsd db4 api to store pmpkg_t and wanted to share it with anyone (interested ?) i have coded 3 utilities: - one that converts pacman's db into a bsd db4 fil

Re: [pacman-dev] [PATCH] bash_completion: remove absolute utility paths again

2010-02-25 Thread solsTiCe d'Hiver
> add a “\” (back-slash) before the command)... it is even working if \ is in the middle of the command name try: $ l\s $ alias printf='print hi\n"' and then try $ prin\tf from #b...@irc.freenode.net you can also use 'command' or "command" or l\s or ''ls