yaourt: pacman frontend

eyolf · 2007-05-10 17:43:24

Great - thanks! I'll have a look at it. Not that I'm a screen guru, but now that I know what to look for, it might be easier.

Shirakawasuna · 2007-05-11 07:05:57

I've experienced the same issue as emphire, with my own package even. yaourt -Su --aur gives "a7xpg: Unable to read a7xpg's PKGBUILD". yaourt -S a7xpg works fine.

Shirakawasuna · 2007-05-15 01:10:44

It also seems like yaourt is adding cruft for some packages using -S. For instance for doing yaourt -S gprename, the gtk2-perl and glib-perl dependencies are required. After those packages install and the gprename installation is complete, it says:

checking dependencies... done.

Targets: gtk2-perl  cairo-perl  glib-perl

Do you want to remove these packages? [Y/n] n

Apparently this is asking if I want to keep them explicitly installed - I thought yaourt could install dependencies *as* dependencies of the package. Doing pacman -Rsc gprename does not remove glib-perl or gtk2-perl, and the packages do not show up in pacman -Qe. Had I not noticed, I'd have three new cruft packages: glib-perl, gtk2-perl, and the dependency cairo-perl.

(note: avoiding this kind of thing is exactly why I dropped aurbuild - any fix is greatly appreciated!)

Last edited by Shirakawasuna (2007-05-15 01:11:14)

wain · 2007-05-15 16:55:16

Shirakawasuna wrote:

It also seems like yaourt is adding cruft for some packages using -S. For instance for doing yaourt -S gprename, the gtk2-perl and glib-perl dependencies are required. After those packages install and the gprename installation is complete, it says:
checking dependencies... done.

Targets: gtk2-perl  cairo-perl  glib-perl

Do you want to remove these packages? [Y/n] n
Apparently this is asking if I want to keep them explicitly installed - I thought yaourt could install dependencies *as* dependencies of the package. Doing pacman -Rsc gprename does not remove glib-perl or gtk2-perl, and the packages do not show up in pacman -Qe. Had I not noticed, I'd have three new cruft packages: glib-perl, gtk2-perl, and the dependency cairo-perl.
(note: avoiding this kind of thing is exactly why I dropped aurbuild - any fix is greatly appreciated!)

This is due to the new makepkg3. I have to write a patch ASAP

for "Unable to read PKGBUILD" problem, I have found a solution for the next release ;-)

mutlu_inek · 2007-05-16 21:04:57

wain wrote:

for "Unable to read PKGBUILD" problem, I have found a solution for the next release ;-)

You are outstanding. We are all deeply indebted to your work. Keep it up!

wain · 2007-05-24 22:03:34

- version 0.7.9-1 -

- fixed wget -c for aur's PKGBUILD (thanks to Florian Loitsch)
- yaourt -Sg show group without root/sudo (thanks to Marc Poiroud)
- yaourt -Si show "last update" for aur's package (Nak)
- new dynamic title for xterm/aterm/rxvt
- makedepends for makepkg are not removed until this bug is not fixed:
http://bugs.archlinux.org/task/7193

stonecrest · 2007-05-24 22:09:00

wain wrote:

- makedepends for makepkg are not removed until this bug is not fixed:
http://bugs.archlinux.org/task/7193

/me votes for it

Beini · 2007-06-06 19:53:04

I'm not sure if this is yaourt related or PKGBUILD related... Im new to arch, just made the switch from gentoo

When I'm trying to install lib32-libart-lgpl from aur, i get this error:

./PKGBUILD: line 21: `install-dir': not a valid identifier

I can make the package manually with makepkg without problems.

wain · 2007-06-07 16:18:09

Beini wrote:

I'm not sure if this is yaourt related or PKGBUILD related... Im new to arch, just made the switch from gentoo
When I'm trying to install lib32-libart-lgpl from aur, i get this error:
./PKGBUILD: line 21: `install-dir': not a valid identifier
I can make the package manually with makepkg without problems.

hum, there is a problem with "source ./PKGBUILD" in yaourt with this extra install-dir function. I don't know how to solve this at this time.
Maybe the solution is to move this line in the build() function as DaNiMoTh wrote on AUR.

build() {
  mkdir -p $startdir/pkg/opt/lib32/usr/
  cp -rPf $startdir/src/usr/lib $startdir/pkg/opt/lib32/usr/lib
}

Last edited by wain (2007-06-07 16:18:34)

nesl247 · 2007-06-12 03:25:57

Anyway to make installing a package from aur not display all the comments?

stonecrest · 2007-06-12 05:34:38

nesl247 wrote:

Anyway to make installing a package from aur not display all the comments?

I agree, it's pretty irritating for packages that have REALLY long comments.

Also, I get a bug that I think is caused by using an alternative --tmp directory:

$ yaourt -S vmware-player --tmp tmp/

...

/usr/bin/yaourt: line 1122: tmp//yaourt-tmp-stonecrest/orphans/orphans_after.13239.tmp: No such file or directory
/usr/bin/yaourt: line 1123: tmp//yaourt-tmp-stonecrest/orphans/installed_after.13239: No such file or directory
/usr/bin/yaourt: line 1124: tmp//yaourt-tmp-stonecrest/orphans/installed_after.13239.newonly: No such file or directory
/usr/bin/yaourt: line 1125: tmp//yaourt-tmp-stonecrest/orphans/orphans_after.13239: No such file or directory
comm: tmp//yaourt-tmp-stonecrest/orphans/orphans_before.13239: No such file or directory

wain · 2007-06-12 11:31:24

nesl247 wrote:

Anyway to make installing a package from aur not display all the comments?

Ok I will add an option

stonecrest wrote:

Also, I get a bug that I think is caused by using an alternative --tmp directory:

$ yaourt -S vmware-player --tmp tmp/

...

/usr/bin/yaourt: line 1122: tmp//yaourt-tmp-stonecrest/orphans/orphans_after.13239.tmp: No such file or directory
/usr/bin/yaourt: line 1123: tmp//yaourt-tmp-stonecrest/orphans/installed_after.13239: No such file or directory
/usr/bin/yaourt: line 1124: tmp//yaourt-tmp-stonecrest/orphans/installed_after.13239.newonly: No such file or directory
/usr/bin/yaourt: line 1125: tmp//yaourt-tmp-stonecrest/orphans/orphans_after.13239: No such file or directory
comm: tmp//yaourt-tmp-stonecrest/orphans/orphans_before.13239: No such file or directory

Sorry, you have to pass the full path like yaourt -S vmware-player --tmp /home/stonecrest/tmp/

Last edited by wain (2007-06-12 11:32:01)

nesl247 · 2007-06-12 16:19:14

Thanks in advance for the not showing of comment option. You think we could have it as default, or have some sort of line in pacman.conf to disable it, so that we don't have to pass --no-comments or something to yaourt?

wain · 2007-06-12 18:10:51

nesl247 wrote:

Thanks in advance for the not showing of comment option. You think we could have it as default, or have some sort of line in pacman.conf to disable it, so that we don't have to pass --no-comments or something to yaourt?

what do you prefer ?
It's easy to add an alias in .bashrc like "alias yaourt='yaourt --showcomment'" or "alias yaourt='yaourt --nocomment'"

nesl247 · 2007-06-12 19:11:39

I'd default it to off. There's really no reason to show comments unless you want to see them.

stonecrest · 2007-06-13 03:14:57

wain wrote:

Sorry, you have to pass the full path like yaourt -S vmware-player --tmp /home/stonecrest/tmp/

Hmm.. yaourt uses the relative tmp path I specified just fine, right up until after the package is installed and I see those lines. Maybe I'm not understanding you correctly. Are you saying that specifying the full path will prevent those error messages? Or will this be changed in the future to allow relative paths?

congyiwu · 2007-06-14 06:31:02

Whenever pacman gives me a Y/n prompt, pressing 'enter' will choose the default. Pressing random letters or the arrow keys doesn't do anything. However, when yaourt gives me a prompt for building/installing packages from the AUR, almost any key will automatically answer the prompt, and show the PKGBUILD, build the pkg, etc. Maybe I'm just being clumsy, but I've accidentally answered a few of these prompts already by trying to change terminals in yakuake with shift+right, except not pressing shift, etc. I think it would be better to only allow the enter key, plus whatever the actual letter choices are for these prompts.

Anyway, I used to use qpkg, and once I realized that qpkg wasn't being developed anymore, I switched to aurbuild, and once aurbuild wasn't being developed anymore, I started using yaourt, which is much faster than aurbuild, btw. I like yaourt a lot so far. Keep up the good work.

nesl247 · 2007-06-14 08:17:14

The prompt() should be changed to contain read -ep "<content of question> y/n etc" <variable name>, instead of the current method of posting the question, then asking yes/no.

wain · 2007-06-18 17:17:44

stonecrest wrote:

wain wrote:
Sorry, you have to pass the full path like yaourt -S vmware-player --tmp /home/stonecrest/tmp/
Hmm.. yaourt uses the relative tmp path I specified just fine, right up until after the package is installed and I see those lines. Maybe I'm not understanding you correctly. Are you saying that specifying the full path will prevent those error messages? Or will this be changed in the future to allow relative paths?

Yes, specifying the full path can prevent those errors, but Yaourt 0.8 will accept relative paths too :-)

nesl247 wrote:

I'd default it to off. There's really no reason to show comments unless you want to see them.

Ok, yaourt will show comment by default. But finally, several users convinced me to add a config file. You will be able to desactivate AUR comments here.

nesl247 wrote:

The prompt() should be changed to contain read -ep "<content of question> y/n etc" <variable name>, instead of the current method of posting the question, then asking yes/no.

-e option is exactly what we need for the problem with arrow keys \o/ thanks a lot !
But the yaourt's behavior which consists in taking only one letter is so much faster

Last edited by wain (2007-06-18 17:29:46)

Shirakawasuna · 2007-06-19 22:35:12

Sorry if what I'm about to report has been talked about already, but I swear I searched for it and searched for it! As I'm sure everyone has noticed, yaourt downloads the source for its packages for every package every time it is run - this means that if you install say 'legends' with yaourt, it downloads the source and attempts to install. If this install fails and you want to install it again, you'll have to redownload the source. This becomes something of a chore if the PKGBUILD has issues (or the user's system) and it would be convenient to be able to specify, possibly in a conf file, to save the source unless a command like yaourt -Scc --aur was run.

It really does seem like someone would have brought this issue up, so again sorry if it's bee gone through!

nesl247 · 2007-06-19 22:37:30

I'm not sure how yaourt works in terms of downloading packages from aur. But this is what could happen

It changes to /tmp
Downloads the .tar.gz
Extracts
Changes to the directory
Builds
If fail, let the person know, but keep the directory

If it's run again, and the version from aur matches the version in the /tmp/<pkgname>/PKGBUILD (if /tmp/<pkgname> is there), then it dosn't redownload.

wain · 2007-06-20 17:44:11

Shirakawasuna wrote:

Sorry if what I'm about to report has been talked about already, but I swear I searched for it and searched for it! As I'm sure everyone has noticed, yaourt downloads the source for its packages for every package every time it is run - this means that if you install say 'legends' with yaourt, it downloads the source and attempts to install. If this install fails and you want to install it again, you'll have to redownload the source. This becomes something of a chore if the PKGBUILD has issues (or the user's system) and it would be convenient to be able to specify, possibly in a conf file, to save the source unless a command like yaourt -Scc --aur was run.
It really does seem like someone would have brought this issue up, so again sorry if it's bee gone through!

Oh that's very easy
Just add "SRCDEST=/some/where/src" in /etc/makepkg.conf

tockar · 2007-06-20 22:24:23

Small bug with --aur:

==> Searching for new version on AUR
(...)
kernel26viper: /usr/bin/yaourt: line 993: [: i: integer expression expected
/usr/bin/yaourt: line 994: [: i: integer expression expected
up to date

Yaourt has this problem only with kernel26viper.

Shirakawasuna · 2007-06-21 08:29:00

wain wrote:

Just add "SRCDEST=/some/where/src" in /etc/makepkg.conf

Awesome, thanks!

Was this in any of the documentation, by the way?

byte · 2007-06-21 11:59:51

man makepkg, man makepkg.conf (PKGDEST/SRCDEST)

Arch Linux

#101 2007-05-10 17:43:24

Re: yaourt: pacman frontend

#102 2007-05-11 07:05:57

Re: yaourt: pacman frontend

#103 2007-05-15 01:10:44

Re: yaourt: pacman frontend

#104 2007-05-15 16:55:16

Re: yaourt: pacman frontend

#105 2007-05-16 21:04:57

Re: yaourt: pacman frontend

#106 2007-05-24 22:03:34

Re: yaourt: pacman frontend

#107 2007-05-24 22:09:00

Re: yaourt: pacman frontend

#108 2007-06-06 19:53:04

Re: yaourt: pacman frontend

#109 2007-06-07 16:18:09

Re: yaourt: pacman frontend

#110 2007-06-12 03:25:57

Re: yaourt: pacman frontend

#111 2007-06-12 05:34:38

Re: yaourt: pacman frontend

#112 2007-06-12 11:31:24

Re: yaourt: pacman frontend

#113 2007-06-12 16:19:14

Re: yaourt: pacman frontend

#114 2007-06-12 18:10:51

Re: yaourt: pacman frontend

#115 2007-06-12 19:11:39

Re: yaourt: pacman frontend

#116 2007-06-13 03:14:57

Re: yaourt: pacman frontend

#117 2007-06-14 06:31:02

Re: yaourt: pacman frontend

#118 2007-06-14 08:17:14

Re: yaourt: pacman frontend

#119 2007-06-18 17:17:44

Re: yaourt: pacman frontend

#120 2007-06-19 22:35:12

Re: yaourt: pacman frontend

#121 2007-06-19 22:37:30

Re: yaourt: pacman frontend

#122 2007-06-20 17:44:11

Re: yaourt: pacman frontend

#123 2007-06-20 22:24:23

Re: yaourt: pacman frontend

#124 2007-06-21 08:29:00

Re: yaourt: pacman frontend

#125 2007-06-21 11:59:51

Re: yaourt: pacman frontend

Board footer