April 2009 - Aur-general - lists.archlinux.org

[aur-general] gpgme03 from unsupported?
by Chris Brannon 07 Apr '09

07 Apr '09

I found this one while looking for orphans, and it seems like a candidate for deletion, since gpgme is already in extra. Any objections? -- Chris

3 2

[aur-general] OneSwarm in AUR wants to update itself
by Mathias Burén 07 Apr '09

07 Apr '09

Hi, I just created a package for OneSwarm [1] and uploaded it to the AUR [2]. The package works fine except that it has an auto-update feature, which of course doesn't work since the user does not have write access to /opt/OneSwarm. What is the correct way of dealing with this? Should I make /opt/OneSwarm writable by the users group? Thanks, Mathias [1] http://oneswarm.cs.washington.edu/ [2] http://aur.archlinux.org/packages.php?ID=25245

5 7

[aur-general] First Package
by Lucas Salies Brum 07 Apr '09

07 Apr '09

My first package in AUR was submitted today, someone could check to see if I did not crap? http://aur.archlinux.org/packages.php?ID=19751 Thank you. --- Lucas Saliés Brum http://sistematico.org lsbrum @ irc.freenode.org

6 7

[aur-general] Adoptable AUR packages
by Ashok Gautham 07 Apr '09

07 Apr '09

There are three kinds of orphans in AUR at the moment. 1) A sea of packages that have either become obselete or have been added in some other package. ( Like dolphin ). 2) The others are ruby/python/perl libraries. The problem with these is that installing them using pyPI or gems is quite simple (though not highly recommended). So many of these get orphaned 3) The last category is where maintainers do not have the time to do justice to their packages and hence orphan it. I found I had a little free time and could adopt some packages. I found myself in this sea. It would be good if we can start a wiki page where every "useful" package that is currently orphaned can be added and removed once adopted. I checked out the wiki. The AUR cleanup day is the closest I got to. We would need something like an inverse of that now. So any user who wants to adopt a package should go to the page, choose whatever he wants to adopt and remove it from the page. I feel this will clear up a lot of packages in the second and last categories. Also, we can give a guideline for people who disown packages to add it to the corresponding page (obselete/required) in the hope that someone will take over the package --- Ashok `ScriptDevil` Gautham

6 8

Re: [aur-general] Maintainer vs Contributor tag let's find a solution ; )
by Loui Chang 07 Apr '09

07 Apr '09

On Mon, Apr 06, 2009 at 12:43:41PM +1000, Allan McRae wrote: > # Maintainer: Joe User <joe.user(a)example.com> > > Note the use of Maintainer... In the end, it is a comment and nothing more > so who really cares about this. Yep.

10 13

Re: [aur-general] Maintainer vs Contributor tag let's find a solution ; )
by Loui Chang 07 Apr '09

07 Apr '09

On Tue, Apr 07, 2009 at 10:56:33AM +1000, Allan McRae wrote: > My summary of this: > > 1) Maintainer tag: It is a comment - makepkg does not care so nor should > you > > 2) $foo vs ${foo} : they do the same thing (except in rare cases where > brackets are needed...) - makepkg does not care so nor should you. > > 3) "$srcdr" vs $srcdir. The quotes are good for people who build in > directories with spaces in their name - so it may be good to use quotes. > But I don't care about people who use spaces in directory names, so I am not > going to do this. Note the prototype does include quotes... > > 4) $startdir/src vs $srcdir. $srcdir is correct. As stated in the > PKGBUILD man page, there is no guarantee that these will continue to point > at the same directory in future pacman versions. Case closed!

1 0

[aur-general] Deletion request
by Thomas Jost 07 Apr '09

07 Apr '09

Hi, I uploaded the wrong PKGBUILD on [1] (it was supposed to be kernel26-source, but I uploaded kernel26 instead...). Could someone please delete this package? Thanks in advance and sorry for the inconvenience. Thomas [1] http://aur.archlinux.org/packages.php?ID=23126

2 1

[aur-general] How to handle interchangeable dependencies?
by hollunder＠gmx.at 07 Apr '09

07 Apr '09

Hi there. I'm looking for a clean way to handle packages that can replace others. Examples: lash can be substituted by lash-git, it works fine, except namcap complains: hydrogen-svn E: Dependency detected and not included (lash-git) from files ['usr/bin/hydrogen'] hydrogen-svn W: Dependency included and not needed (lash) Adding 'lash' or 'lash=0.6.0' to the provides array of lash-git doesn't help. I have the same situation with for example jack-audio-connection-kit where we have quite a number of different packages that all provide the same basic functionality and are interchangeable. Note that it mostly works with provides, it just isn't clean and there are cases where it can break stuff. Is there a solution to this? Best regards, Philipp

8 23

[aur-general] Request deletion lv2-c++-tools
by hollunder＠gmx.at 06 Apr '09

06 Apr '09

http://aur.archlinux.org/packages.php?ID=23651 It seems like the c++ in the name causes problems, at least with yaourt. I made a new package with cpp instead. Philipp

4 6

[aur-general] AUR package removal request
by revel 06 Apr '09

06 Apr '09

Hello, Please remove [1] from AUR. I changed the package name to [2] some time ago and kept [1] in kind of deprecated state. [1] http://aur.archlinux.org/packages.php?ID=15158 [2] http://aur.archlinux.org/packages.php?ID=22238 -- revel

2 1