Clyde - A better libalpm/makepkg wrapper

Japanlinux · 2010-05-21 06:28:01

lymphatik, thank you for the fast reply

I didn't know I could update programs installed from AUR with --aur. that is a fantastic piece of info you just gave me, so thanks again

well, I guess makepkg is the only way to install this. good to know.

ijanos · 2010-05-21 06:37:55

Japanlinux wrote:

well, I guess makepkg is the only way to install this. good to know.

Yes it is. It is intentional, because AUR is unspported (and potentionally dangerous), it is only recommended to users who know what are they doing.

Read this: http://wiki.archlinux.org/index.php/AUR_Quickstart

Japanlinux · 2010-05-21 06:41:15

well, I have clyde now and am installing Google Chrome (it was my favorite browser on Windows). as it installed, a crazy amount of text zoomed through the terminal. is that normal? and if it is, why would anyone want to see that stuff?

I read that page you linked to and noticed something strange. It says in the end pacman -U ... .gz. However, when i went through the steps, my package ended in xz. is that a typo?

Last edited by Japanlinux (2010-05-21 06:43:25)

FaN_OnLy1 · 2010-05-21 06:48:12

The crazy amount of text you see scrolling through the terminal is the compile (make) output. And as to why would want to see that stuff, we do, because it can help determine what's wrong in a package if it doesn't compile at all.

*tar.xz is the new package extension pacman uses, it uses a stronger compression algorithm thus permiting smaller package sizes.

ijanos · 2010-05-21 06:52:22

Japanlinux wrote:

well, I have clyde now and am installing Google Chrome (it was my favorite browser on Windows). as it installed, a crazy amount of text zoomed through the terminal. is that normal? and if it is, why would anyone want to see that stuff?

I think chromium package is available from the extra repository, no need to use AUR for that. The crazy amount of text is usual if you compile a program for yourself. You can see what is going on currently and if something goes wrong, hopefully you can tell from the last few lines.

I read that page you linked to and noticed something strange. It says in the end pacman -U ... .gz. However, when i went through the steps, my package ended in xz. is that a typo?

Not a typo, It was changed recently from gz to xz so dont worry about that.

SanskritFritz · 2010-05-21 07:59:15

IMHO it is far easier for a beginner to put this line into /etc/pacman.conf:

[archstuff]
# AUR's most voted packages
Server=http://archstuff.vs169092.vserver.de/i686

And then
pacman -S clyde

ijanos · 2010-05-21 08:12:33

SanskritFritz wrote:

IMHO it is far easier for a beginner to put this line into /etc/pacman.conf

Yeah, but then users wont learn what is AUR and how it works. Not to mention that adding random repos is as much dangerous as building random stuff from AUR.

Daenyth · 2010-05-21 09:58:43

Moreso, because you have no oversight.

Japanlinux · 2010-05-22 03:58:16

Well, when I tried to makepkg for clyde, I didn't like how it installed to my /home/USER folder. I wanted it installed how all other programs are installed. So I tried the repo above. I have an x86_64, but that repo didn't have it. So I used the i686 repo, and installed clyde. Well, turns out that was a mistake, since lua didn't like that I wasn't using a 32bit system (i assume that is what it means by wrong ELF class: ELFCLASS32). But now I can't uninstall clyde or lualpm. I did install lualpm after that, which also upgraded clyde. But i guess that doesn't stop clyde from using the other lualpm. so how do I do remove the 32bit lualpm/clyde?

I would also prefer to completely remove clyde and it's dependents and try makepkg again, with some guidance from here. How can I use makepkg to install clyde like a normal program, instead of it operating out of my home folder?

EDIT: thought I'd add the steps i use to makepkg...

wget http://aur.archlinux.org/packages/clyde-git/clyde-git/PKGBUILD
makepkg -s
pacman -u clyde-git-20100522-1-x86_64.pkg.tar.xz

Last edited by Japanlinux (2010-05-22 04:13:11)

anonymous_user · 2010-05-22 05:21:46

When you installed the tar.xz with pacman, you ran it as root right?

Also if you have any other AUR helper installed, you could try using it to install Clyde.

Last edited by anonymous_user (2010-05-22 05:22:21)

Japanlinux · 2010-05-22 05:36:53

lol... I guess root would help

well i feel kinda dumb for that... Thanks for the tip

ijanos · 2010-05-22 06:30:50

Japanlinux wrote:

EDIT: thought I'd add the steps i use to makepkg...

wget http://aur.archlinux.org/packages/clyde-git/clyde-git/PKGBUILD
makepkg -s
pacman -u clyde-git-20100522-1-x86_64.pkg.tar.xz

I'd like to point out that pacman's options are case sensitive, you want to use -U and not -u

And of coures use sudo or other means of root privilage.

Last edited by ijanos (2010-05-22 06:33:20)

Kiwi · 2010-05-22 12:08:12

Ok, I do not know why the it_IT-UTF-8 locale is not working for Berseker, as I just tested it and it worked fine; I have not changed anything with regards to that.

I have also made it so you do not need sudo anymore, as long as you either use '--user youruser' or set 'BuildUser = youruser' in clyde.conf, then you can install from AUR safely.

"clyde <search query> => numbers" behavior likewise now works if you do not have sudo, at least it should...note that passing additional arguments to this will not have any effect (It will outright fail in yaourt, btw).

I will try to get in zsh and bash completion later today. I do not know if I will have time for much else but I will probably try to get as much done on it as I can...Sunday is right out, though; it is my birthday on Monday, so I am going to Worlds of Fun (a pretty cool amusement park).

I am also trying to update the man page, but it is being a pita. >.>

orschiro · 2010-05-22 19:01:15

Hmm I tried the method without sudo but it isn't working. Here the error:

[orschiro@thinkpad ~]$ clyde --user orschiro -Syu
error: you cannot perform this operation unless you are root.

And yes of course I updated clyde-git.

Kiwi · 2010-05-22 19:41:16

su first.

orschiro · 2010-05-22 20:12:15

Thank you Kiwi.

So running clyde as normal user comes again with the need of sudo or is there another way to perform the actions as normal user without becoming root with su first?

Kiwi · 2010-05-22 20:27:48

To install something with clyde, or pacman, or anything that uses libalpm (directly or indirectly), the program that does actual installation (in wrappers this is pacman, in clyde it is clyde) has to run as root by some means.

This patch just makes it so that that some means is not required to be sudo.

EDIT: zsh and bash completion added!

Last edited by Kiwi (2010-05-22 23:03:49)

Duca · 2010-05-23 07:21:41

Kiwi, i am in doubt about the behavior in clyde regarding root password request. When i typed:

clyde gccucp

which is an AUR package, clyde successfully listed it as an AUR package (1 AUR/gccucp ), then i selected it and clyde asked for the root password.

Password:
:: gccucp package not found, searching for group...
:: gccucp group not found, searching AUR...
==> Installing the following packages from AUR
Targets (1): gccucp

==> Proceed with installation? [Y/n] y
==> Downloading gccucp.tar.gz
    ( Unsupported package from AUR: Potentially dangerous! )
==> Edit the PKGBUILD (highly recommended for security reasons)? [Y/n]
==> Running makepkg as root is a bad idea!
==> To avoid this message please set BuildUser in clyde.conf
==> Continue anyway? [y/N] n

I set a BuildUser line in my clyde.conf (I assume it meant /etc/clyde.conf)

Editor = vim
#Colors are enabled by default. To disable them, uncomment the following line
#NoColor
#Searching AUR is enabled by default. Uncomment the following line to only sear$
#ReposOnly
#
BuildUser = eduardo

I liked the idea of setting a different user to build the package, but after i added the mentionated line in my clyde.conf, i still got the same message, is it possible to have the BuildUser in the clyde.conf as a commented line? Or have clyde to detect the user that executed it to build the AUR packages as a default behavior (and still keep the BuildUser as an option) ?

I also have a feature request: after building an aur package, to have it saved in ~/.clyde or /var/cache/pacman/... or somewhere else (it would be awesome if it were configurable) to avoid the sometimes extensive build up times.

Last edited by Duca (2010-05-23 07:41:24)

Kiwi · 2010-05-23 08:24:25

I cannot reproduce it for whatever reason.

This is how it currently should work....

If you do not have a config and run with super user privileges:
You ran with --user <foo>, but not with sudo; it will create a config with BuildUser = foo set
You ran with --user <foo>, with sudo; it will create a config with BuildUser = foo set
*You ran without a --user, but not with sudo; it will create a config with BuildUser = root
You ran without a --user, with sudo; it will create a config with BuildUser = SUDO_USER (the user you ran sudo as)

You do have a config but no BuildUser set:
You ran without --user <foo>, with sudo; builds as SUDO_USER
*You ran without --user <foo>, as su; builds as root
You ran with --user <foo>, no matter with sudo or su, builds as foo

You do have a config and BuildUser is set:
You ran without --user <foo>, builds as BuildUser
You ran with --user <foo>, builds as foo
Not dependent on whether you used sudo or su.

All but the asterisked ones should be safe, as long as you do not have BuildUser = root or --user root,

As for that feature, it is planned, in the meantime you can set in makepkg.conf the variable PKGDEST and makepkg will move built packages there, clyde should then find them when it installs (But will not look for it there before building again, there is an open ticket on that too iirc)

Coding talk follows:
Part of the behavior of the scenarios above can be summarized by this code and understanding interactions of config and command line arguments...

function getbuilduser()
    return config.op_s_build_user or os.getenv("SUDO_USER") or "root"
end

op_s_build_user will be one of three things, false by default, BuildUser, or --user foo. If there is --user foo it will override BuildUser if it is set as well (this is how it generally works for other options as well).
If either --user or BuildUser is set it returns that user, else (it is still false) it checks if it was ran with sudo, if it was then it returns the user that ran it, else that is nil so it returns root. This is because that line returns the first thing that is not nil or false.

Daenyth · 2010-05-23 12:55:19

Can't you just have it default to the current user rather than requiring a builduser set or --user? I don't see why a setting is needed.

Kiwi · 2010-05-23 13:33:13

If you login as root then there is no other user...though apparently if you do su as a user it still has the user you ran su as, which I had forgotten about...I will look into it.

[kiwi@lappy:lua/clyde]$ su -c 'lua -e "print(os.getenv(\"USER\"))"'                     (05-23 08:30)
Password: 
kiwi
[kiwi@lappy:lua/clyde]$                                                                 (05-23 08:30)

[kiwi@lappy:lua/clyde]$ su -                                                            (05-23 08:32)
Password: 
[root@lappy ~]# lua -e "print(os.getenv(\"USER\"))"
root
[root@lappy ~]#

Ogion · 2010-05-23 14:13:37

Maybe this helps?:

ogion@Gont ~ % su - root -c 'echo $USER'
Passwort: 
root
ogion@Gont ~ % su - root -c 'lua -e "print(os.getenv(\"USER\"))"' 
Passwort: 
root
ogion@Gont ~ %

Ogion

Duca · 2010-05-23 16:11:38

I see, the first "*" scenario is what i did at first time (stock /etc/clyde.conf)
*You ran without a --user, but not with sudo; it will create a config with BuildUser = root

then i added the BuildUser var, ran without --user and without sudo as well, but apparently it ignored my builduser and sticked with the BuildUser = root

Last edited by Duca (2010-05-23 16:17:48)

benob · 2010-05-25 09:32:52

After trying clyde, here is my wishlist:
- ctrl-c
- one keypress decisions (ex: [Yn], proceed with 'n' instead of 'n<enter>')
- search inside search results with '/' (maybe display search results with a pager)
- better handling of proxy (aur search does not go through)
- reuse partial builds

mythus · 2010-05-25 11:12:35

Greetings,

I have tried out clyde, and it is pretty nice and fast. However, I can't help but to feel there is something I am missing that I liked in yaourt.... that is the ability to simply type yaourt -S packagename versus sudo clyde -S package name.

I am not interested in whatever may be the perceived correct method as I always inspect the package build file anyways, and sure the extra sudo infront of clyde may not be much since yaourt is seemingly longer, but it feels nicer. When I use pacman I always go into su first, so I have my one su - command and then I use pacman - S etc... for whatever I need there. However, you are not supposed to build a package from AUR in su mode and even get a nice warning about it.... but you have to use sudo?

Anyways, the jest of all of my rambling here is, if you can make clyde work without sudo, it will be gold as far as I am concerned.

Arch Linux

#326 2010-05-21 06:28:01

Re: Clyde - A better libalpm/makepkg wrapper

#327 2010-05-21 06:37:55

Re: Clyde - A better libalpm/makepkg wrapper

#328 2010-05-21 06:41:15

Re: Clyde - A better libalpm/makepkg wrapper

#329 2010-05-21 06:48:12

Re: Clyde - A better libalpm/makepkg wrapper

#330 2010-05-21 06:52:22

Re: Clyde - A better libalpm/makepkg wrapper

#331 2010-05-21 07:59:15

Re: Clyde - A better libalpm/makepkg wrapper

#332 2010-05-21 08:12:33

Re: Clyde - A better libalpm/makepkg wrapper

#333 2010-05-21 09:58:43

Re: Clyde - A better libalpm/makepkg wrapper

#334 2010-05-22 03:58:16

Re: Clyde - A better libalpm/makepkg wrapper

#335 2010-05-22 05:21:46

Re: Clyde - A better libalpm/makepkg wrapper

#336 2010-05-22 05:36:53

Re: Clyde - A better libalpm/makepkg wrapper

#337 2010-05-22 06:30:50

Re: Clyde - A better libalpm/makepkg wrapper

#338 2010-05-22 12:08:12

Re: Clyde - A better libalpm/makepkg wrapper

#339 2010-05-22 19:01:15

Re: Clyde - A better libalpm/makepkg wrapper

#340 2010-05-22 19:41:16

Re: Clyde - A better libalpm/makepkg wrapper

#341 2010-05-22 20:12:15

Re: Clyde - A better libalpm/makepkg wrapper

#342 2010-05-22 20:27:48

Re: Clyde - A better libalpm/makepkg wrapper

#343 2010-05-23 07:21:41

Re: Clyde - A better libalpm/makepkg wrapper

#344 2010-05-23 08:24:25

Re: Clyde - A better libalpm/makepkg wrapper

#345 2010-05-23 12:55:19

Re: Clyde - A better libalpm/makepkg wrapper

#346 2010-05-23 13:33:13

Re: Clyde - A better libalpm/makepkg wrapper

#347 2010-05-23 14:13:37

Re: Clyde - A better libalpm/makepkg wrapper

#348 2010-05-23 16:11:38

Re: Clyde - A better libalpm/makepkg wrapper

#349 2010-05-25 09:32:52

Re: Clyde - A better libalpm/makepkg wrapper

#350 2010-05-25 11:12:35

Re: Clyde - A better libalpm/makepkg wrapper

Board footer