Clyde - A better libalpm/makepkg wrapper

Doorbreath · 2010-06-08 11:23:08

Why do I have to specify --aur

dieghen89 · 2010-06-08 11:25:24

I don't know if someone already asks this features:

- allow the clyde -S aur/package
- add the choise of a directory where put the cache of the aur packages
- colorized output also in clyde -Sl repo

@Doorbreath
it works also with clyde -Syua

Last edited by dieghen89 (2010-06-08 11:25:55)

Doorbreath · 2010-06-08 11:35:04

I can install aur packages without --aur but I have to specify --aur or -a to upgrade them?

dieghen89 · 2010-06-08 11:53:22

For the install and search aur is enabled as default...the only command that needs the -a (or --aur) option is the -Su (or -Syu)....

muunleit · 2010-06-12 17:01:59

Doorbreath wrote:

I can install aur packages without --aur but I have to specify --aur or -a to upgrade them?

Yes.

btw, from clyde.conf ...

#Searching AUR is enabled by default. Uncomment the following line to only search with --aur
#ReposOnly

655321 · 2010-06-17 07:01:32

How stable is this? Will it break my system? I want to try it but I have spent lots of time customizing my system and dont want to do lots of work in case it breaks

looks very good though

ngoonee · 2010-06-17 07:05:16

If you're using Arch you'll know how to fix anything it does break, so just go for it .

Moo-Crumpus · 2010-06-17 07:09:54

ngoonee wrote:

If you're using Arch you'll know how to fix anything it does break, so just go for it .

Omg ...

655321 · 2010-06-17 07:12:06

Well, in fact I dont know how to fix ANYTHING lol, Im just learning, but thanks to this forum I can fix anything so, be ready for posts of me calling for help lol

ijanos · 2010-06-17 07:27:44

655321 wrote:

Well, in fact I dont know how to fix ANYTHING lol, Im just learning, but thanks to this forum I can fix anything so, be ready for posts of me calling for help lol

Breaking and fixing things can be part of the learning experinece, especially if you are trying to solve the problemes yourself first.

655321 · 2010-06-17 07:32:35

thats what I meant I learnt more about linux installing arch than using ubuntu for like 2 years now im a lot more proficient at both

leadghost · 2010-06-17 08:26:23

Just a heads up that clyde-git currently won't work with pacman 3.4.0-1 from testing.

$ clyde -Syu
lua: error loading module 'lualpm' from file '/usr/lib/lua/5.1/lualpm.so':
libalpm.so.4: cannot open shared object file: No such file or directory
stack traceback:
[C]: ?
[C]: in function 'require'
/usr/share/lua/5.1/clydelib/util.lua:2: in main chunk
[C]: in function 'require'
/usr/bin/clyde:5: in main chunk
[C]: ?

Allan · 2010-06-17 08:34:06

at a minimum you will need to rebuild it against the current pacman... from experience with shaman, that would usually require so patching.

Liuuutas · 2010-06-17 11:20:44

The rebuilding of the clyde-git fails:

gcc -Wall -W -O2 -fPIC  -lalpm `pkg-config --cflags lua` -shared -o lualpm.so lualpm.c -pedantic -D_FILE_OFFSET_BITS=64 -std=c99 -D_GNU_SOURCE
lualpm.c:277:1: error: 'PM_TRANS_TYPE_UPGRADE' undeclared here (not in a function)
lualpm.c:277:5: warning: missing initializer
lualpm.c:277:5: warning: (near initialization for 'transtype_constants[0].value')
lualpm.c:278:1: error: 'PM_TRANS_TYPE_REMOVE' undeclared here (not in a function)
lualpm.c:278:5: warning: missing initializer
lualpm.c:278:5: warning: (near initialization for 'transtype_constants[1].value')
lualpm.c:279:1: error: 'PM_TRANS_TYPE_REMOVEUPGRADE' undeclared here (not in a function)
lualpm.c:279:5: warning: missing initializer
lualpm.c:279:5: warning: (near initialization for 'transtype_constants[2].value')
lualpm.c:280:1: error: 'PM_TRANS_TYPE_SYNC' undeclared here (not in a function)
lualpm.c:280:5: warning: missing initializer
lualpm.c:280:5: warning: (near initialization for 'transtype_constants[3].value')
lualpm.c:285:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'check_transtype'
lualpm.c:292:30: error: expected declaration specifiers or '...' before 'pmtranstype_t'
lualpm.c: In function 'push_transtype':
lualpm.c:294:29: error: 't' undeclared (first use in this function)
lualpm.c:294:29: note: each undeclared identifier is reported only once for each function it appears in
lualpm.c:294:5: warning: passing argument 2 of 'push_constant' makes integer from pointer without a cast
lualpm.c:222:1: note: expected 'int' but argument is of type 'const struct constant_t *'
lualpm.c: In function 'lalpm_pkg_get_removes':
lualpm.c:806:5: warning: implicit declaration of function 'alpm_pkg_get_removes'
lualpm.c:806:25: warning: initialization makes pointer from integer without a cast
lualpm.c: In function 'lalpm_trans_get_type':
lualpm.c:1910:5: error: 'pmtranstype_t' undeclared (first use in this function)
lualpm.c:1910:5: warning: statement with no effect
lualpm.c:1910:19: error: expected ';' before 'x'
lualpm.c:1911:9: error: 'x' undeclared (first use in this function)
lualpm.c:1915:5: error: too many arguments to function 'push_transtype'
lualpm.c:292:1: note: declared here
lualpm.c: In function 'lalpm_trans_get_pkgs':
lualpm.c:1932:5: warning: implicit declaration of function 'alpm_trans_get_pkgs'
lualpm.c:1932:25: warning: initialization makes pointer from integer without a cast
lualpm.c: In function 'lalpm_trans_init':
lualpm.c:2211:5: error: 'pmtranstype_t' undeclared (first use in this function)
lualpm.c:2211:5: warning: statement with no effect
lualpm.c:2211:19: error: expected ';' before 'type'
lualpm.c:2218:40: error: 'type' undeclared (first use in this function)
lualpm.c:2221:40: error: incompatible type for argument 1 of 'alpm_trans_init'
/usr/include/alpm.h:405:5: note: expected 'pmtransflag_t' but argument is of type 'const struct constant_t *'
lualpm.c:2221:40: error: incompatible type for argument 2 of 'alpm_trans_init'
/usr/include/alpm.h:405:5: note: expected 'alpm_trans_cb_event' but argument is of type 'pmtransflag_t'
lualpm.c:2221:40: warning: passing argument 3 of 'alpm_trans_init' from incompatible pointer type
/usr/include/alpm.h:405:5: note: expected 'alpm_trans_cb_conv' but argument is of type 'void (*)(enum pmtransevt_t,  void *, void *)'
lualpm.c:2221:40: warning: passing argument 4 of 'alpm_trans_init' from incompatible pointer type
/usr/include/alpm.h:405:5: note: expected 'alpm_trans_cb_progress' but argument is of type 'void (*)(enum pmtransconv_t,  void *, void *, void *, int *)'
lualpm.c:2221:40: error: too many arguments to function 'alpm_trans_init'
/usr/include/alpm.h:405:5: note: declared here
lualpm.c: In function 'lalpm_trans_sysupgrade':
lualpm.c:2230:5: warning: implicit declaration of function 'alpm_trans_sysupgrade'
lualpm.c: In function 'lalpm_trans_addtarget':
lualpm.c:2242:5: warning: implicit declaration of function 'alpm_trans_addtarget'
make: *** [lualpm] Error 1
    Aborting...

falconindy · 2010-06-17 15:23:16

ABI changes in libalpm mean that the lualpm bindings need updating. Until Kiwi or other does this, Clyde's broken with testing/pacman.

smartboyathome · 2010-06-17 15:50:19

falconindy wrote:

ABI changes in libalpm mean that the lualpm bindings need updating. Until Kiwi or other does this, Clyde's broken with testing/pacman.

I will proceed to not upgrade pacman then, thanks for the heads up.

Allan · 2010-06-17 22:51:25

You would think the PKGBUILD for a pacman/makepkg wrapper would have versioned dependencies on pacman to prevent upgrading pacman and breaking itself...

depends=('pacman=>3.3' 'pacman<3.4')

aeosynth · 2010-06-18 05:13:31

Is this project basically dead? No activity in github since May 22, no author response to build failure....

edit: er, disregard the last part; build failure was only reported today.

Last edited by aeosynth (2010-06-18 05:19:14)

Allan · 2010-06-18 06:19:16

Not dead... the author has a paid job deadline and developing clyde still does not pay the bills!

gtklocker · 2010-06-18 06:24:59

Ghost1227, could you add pacman's new features to clyde? :-)

@aeosmith: the package 'clyde-git' was build successfully yesterday.

Last edited by gtklocker (2010-06-18 06:26:09)

scio · 2010-06-18 12:55:22

You guys are also forgetting, it currently only breaks if you use [testing]. The new pacman hasn't hit [core] yet.

Kiwi · 2010-06-18 18:14:27

Allan wrote:

You would think the PKGBUILD for a pacman/makepkg wrapper would have versioned dependencies on pacman to prevent upgrading pacman and breaking itself...
depends=('pacman=>3.3' 'pacman<3.4')

Ghost1227 is in charge of the PKGBUILD and Makefile (actually that is about all he does...)

Anyway, someone patched it for me, I have not tested it yet or looked at the code too much, but here is his git tree.

http://github.com/juster/clyde.git

If anyone using [testing] wants to test it just edit the PKGBUILD to use that instead. Let me know if you find anything wrong and I will try to find time to get it fixed, or try to get him to fix it, or you can fix it yourself and submit a patch.

P.S. I am going on vacation for a few days and leave Sunday at 6 am (central), so do not expect me to do anything around that time, though I might have a tiny bit of internet/time while out there. Ghost1227 can probably hack on it, though...Allan breaks stuff, Ghost1227 fixes it.

Lake Mille Lacs (MN), here I come! Mmm, walleye...

bjesus · 2010-06-18 23:33:38

Kiwi wrote:

Allan wrote:
You would think the PKGBUILD for a pacman/makepkg wrapper would have versioned dependencies on pacman to prevent upgrading pacman and breaking itself...
depends=('pacman=>3.3' 'pacman<3.4')
Ghost1227 is in charge of the PKGBUILD and Makefile (actually that is about all he does...)
Anyway, someone patched it for me, I have not tested it yet or looked at the code too much, but here is his git tree.
http://github.com/juster/clyde.git
If anyone using [testing] wants to test it just edit the PKGBUILD to use that instead. Let me know if you find anything wrong and I will try to find time to get it fixed, or try to get him to fix it, or you can fix it yourself and submit a patch.
P.S. I am going on vacation for a few days and leave Sunday at 6 am (central), so do not expect me to do anything around that time, though I might have a tiny bit of internet/time while out there. Ghost1227 can probably hack on it, though...Allan breaks stuff, Ghost1227 fixes it.
Lake Mille Lacs (MN), here I come! Mmm, walleye...

Just to let you know - this git branch works well with pacman 3.4.0-1 from testing. thank you!

UPDATE: oh, wait, it's not...

when trying to install something from AUR, it fails with this:

==> Installing the following packages from repos
lua: /usr/share/lua/5.1/clydelib/util.lua:455: attempt to call method 'pkg_get_removes' (a nil value)
stack traceback:
    /usr/share/lua/5.1/clydelib/util.lua:455: in function 'display_synctargets'
    /usr/share/lua/5.1/clydelib/sync.lua:1474: in function 'sync_trans'
    /usr/share/lua/5.1/clydelib/sync.lua:1623: in function 'clyde_sync'
    /usr/share/lua/5.1/clydelib/sync.lua:1629: in function </usr/share/lua/5.1/clydelib/sync.lua:1628>
    (tail call): ?
    /usr/bin/clyde:1032: in function </usr/bin/clyde:943>
    (tail call): ?
    [C]: ?

Last edited by bjesus (2010-06-18 23:35:50)

juster · 2010-06-19 04:06:38

Please try again, I fixed that pkg_get_removes bug. I forgot to remove the call to it from the lua code. It is a removed function from libalpm.

I created a PKGBUILD, copy & paste this wget to download it

wget http://xrl.us/clydepkg

Then run makepkg, pacman -U on it. The package is called clyde-fork-git.

edit: used xrl.us URL alias for easy typing

Last edited by juster (2010-06-19 18:46:20)

Berseker · 2010-06-19 08:11:41

juster wrote:

Please try again, I fixed that pkg_get_removes bug. I forgot to remove the call to it from the lua code. It is a removed function from libalpm.
I created a PKGBUILD, copy & paste this wget to download it
wget http://github.com/juster/clyde/raw/pacman3.4/PKGBUILD
Then run makepkg, pacman -U on it. The package is called clyde-fork-git.

i renamed the package clyde-git and it works well. Thanks to all who have worked on the patch

Arch Linux

#376 2010-06-08 11:23:08

Re: Clyde - A better libalpm/makepkg wrapper

#377 2010-06-08 11:25:24

Re: Clyde - A better libalpm/makepkg wrapper

#378 2010-06-08 11:35:04

Re: Clyde - A better libalpm/makepkg wrapper

#379 2010-06-08 11:53:22

Re: Clyde - A better libalpm/makepkg wrapper

#380 2010-06-12 17:01:59

Re: Clyde - A better libalpm/makepkg wrapper

#381 2010-06-17 07:01:32

Re: Clyde - A better libalpm/makepkg wrapper

#382 2010-06-17 07:05:16

Re: Clyde - A better libalpm/makepkg wrapper

#383 2010-06-17 07:09:54

Re: Clyde - A better libalpm/makepkg wrapper

#384 2010-06-17 07:12:06

Re: Clyde - A better libalpm/makepkg wrapper

#385 2010-06-17 07:27:44

Re: Clyde - A better libalpm/makepkg wrapper

#386 2010-06-17 07:32:35

Re: Clyde - A better libalpm/makepkg wrapper

#387 2010-06-17 08:26:23

Re: Clyde - A better libalpm/makepkg wrapper

#388 2010-06-17 08:34:06

Re: Clyde - A better libalpm/makepkg wrapper

#389 2010-06-17 11:20:44

Re: Clyde - A better libalpm/makepkg wrapper

#390 2010-06-17 15:23:16

Re: Clyde - A better libalpm/makepkg wrapper

#391 2010-06-17 15:50:19

Re: Clyde - A better libalpm/makepkg wrapper

#392 2010-06-17 22:51:25

Re: Clyde - A better libalpm/makepkg wrapper

#393 2010-06-18 05:13:31

Re: Clyde - A better libalpm/makepkg wrapper

#394 2010-06-18 06:19:16

Re: Clyde - A better libalpm/makepkg wrapper

#395 2010-06-18 06:24:59

Re: Clyde - A better libalpm/makepkg wrapper

#396 2010-06-18 12:55:22

Re: Clyde - A better libalpm/makepkg wrapper

#397 2010-06-18 18:14:27

Re: Clyde - A better libalpm/makepkg wrapper

#398 2010-06-18 23:33:38

Re: Clyde - A better libalpm/makepkg wrapper

#399 2010-06-19 04:06:38

Re: Clyde - A better libalpm/makepkg wrapper

#400 2010-06-19 08:11:41

Re: Clyde - A better libalpm/makepkg wrapper

Board footer