[aur-general] How to include sources from sourceforge + creating links not provided by package

newer
[aur-general] provides version for...

Javier Vasquez

24 Nov 2009 24 Nov '09

3:46 a.m.

Hi, I'd like to know how to specify sources coming from sorceforge in PKGBUILD, and example could work just fine. Also I'd like to know how to create a link automatically once the package has been installed. This implies removing it when removing the package. If necessary, checking if the link exists when upgrading the package (if the package gets removed before installing new version, that might be handled by the removing of the link when removing the package)... Thanks, -- Javier.

Show replies by date

Ranguvar

24 Nov 24 Nov

3:54 a.m.

New subject: [aur-general] How to include sources from sourceforge + creating links not provided by package

On Mon, Nov 23, 2009 at 10:46 PM, Javier Vasquez wrote:

...

Hi,

I'd like to know how to specify sources coming from sorceforge in PKGBUILD, and example could work just fine.

Also I'd like to know how to create a link automatically once the package has been installed. This implies removing it when removing the package. If necessary, checking if the link exists when upgrading the package (if the package gets removed before installing new version, that might be handled by the removing of the link when removing the package)...

Thanks,

-- Javier.

Hey Javier, For SourceForge, you can use http://downloads.sourceforge.net/. Go to the project, get to where it asks to download. It will also offer a direct link. Copy that, and remove the ending bit about which mirror to use, and you have the right URL. For example, for Shareaza: http://downloads.sourceforge.net/project/shareaza/Shareaza/Shareaza%202.5.0.... Obviously, replace the version and such with "$pkgver", etc. downloads.sourceforge.net hands you a close-by mirror. On links, you can just ln -s. For the first argument to ln, don't specify $pkgdir. This is correct for a PKGBUILD, for example: ln -s /opt/foo/foobin "$pkgdir/usr/bin/foobin" The link will be removed on uninstall. Hope that helps, -- Ranguvar

Ray Rashif

6:13 a.m.

New subject: [aur-general] How to include sources from sourceforge + creating links not provided by package

2009/11/24 Ranguvar

...

On links, you can just ln -s. For the first argument to ln, don't specify $pkgdir. This is correct for a PKGBUILD, for example:

ln -s /opt/foo/foobin "$pkgdir/usr/bin/foobin"

The link will be removed on uninstall.

Hope that helps, -- Ranguvar

Just in case the OP takes this literally (and I have reason to believe so) - that is _wrong_ for a _PKGBUILD_, correct for an install scriptlet i.e foobar.install; post_install(), post_remove().

Allan McRae

6:25 a.m.

New subject: [aur-general] How to include sources from sourceforge + creating links not provided by package

Ray Rashif wrote:

...

2009/11/24 Ranguvar

...
On links, you can just ln -s. For the first argument to ln, don't specify $pkgdir. This is correct for a PKGBUILD, for example:

ln -s /opt/foo/foobin "$pkgdir/usr/bin/foobin"

The link will be removed on uninstall.

Hope that helps, -- Ranguvar

Just in case the OP takes this literally (and I have reason to believe so) - that is _wrong_ for a _PKGBUILD_, correct for an install scriptlet i.e foobar.install; post_install(), post_remove().

Huh... it looks the right way to create symlinks in a PKGBUILD to me.

Laszlo Papp

6:32 a.m.

New subject: [aur-general] How to include sources from sourceforge + creating links not provided by package

On Tue, Nov 24, 2009 at 7:25 AM, Allan McRae wrote:

...

Ray Rashif wrote:

...
2009/11/24 Ranguvar

...
On links, you can just ln -s. For the first argument to ln, don't specify $pkgdir. This is correct for a PKGBUILD, for example:

ln -s /opt/foo/foobin "$pkgdir/usr/bin/foobin"

The link will be removed on uninstall.

Hope that helps, -- Ranguvar

Just in case the OP takes this literally (and I have reason to believe so) - that is _wrong_ for a _PKGBUILD_, correct for an install scriptlet i.e foobar.install; post_install(), post_remove().

Huh... it looks the right way to create symlinks in a PKGBUILD to me.

Me too, and I saw this usage in core/extra/community repositories too. Best Regards, Laszlo Papp

Ray Rashif

6:54 a.m.

New subject: [aur-general] How to include sources from sourceforge + creating links not provided by package

2009/11/24 Laszlo Papp

...

On Tue, Nov 24, 2009 at 7:25 AM, Allan McRae wrote:

...
Ray Rashif wrote:

...
2009/11/24 Ranguvar

...
On links, you can just ln -s. For the first argument to ln, don't specify $pkgdir. This is correct for a PKGBUILD, for example:

ln -s /opt/foo/foobin "$pkgdir/usr/bin/foobin"

The link will be removed on uninstall.

Hope that helps, -- Ranguvar

Just in case the OP takes this literally (and I have reason to believe

so)

...
- that is _wrong_ for a _PKGBUILD_, correct for an install scriptlet i.e foobar.install; post_install(), post_remove().

Huh... it looks the right way to create symlinks in a PKGBUILD to me.

Me too, and I saw this usage in core/extra/community repositories too.

Best Regards, Laszlo Papp

crap, read it the wrong way: ln -s $pkgdir/foo foo will evaluate $pkgdir and link there, so eg. $pkgdir/usr is not really /usr. ln -s foo $pkgdir/foo will still refer to the real location so that is fine, right?

Xyne

12:57 p.m.

New subject: [aur-general] How to include sources from sourceforge + creating links not provided by package

On Tue, 24 Nov 2009 14:54:14 +0800 Ray Rashif wrote:

...

crap, read it the wrong way:

ln -s $pkgdir/foo foo will evaluate $pkgdir and link there, so eg. $pkgdir/usr is not really /usr. ln -s foo $pkgdir/foo will still refer to the real location so that is fine, right?

Basically, yeah. The first argument is just text and doesn't need to correspond to any actual path on the system. When the link is read, it returns that text and the system interprets it as a path. The second argument is just the output location where the link should be created. So "ln -s $pkgdir/foo foo" creates a link named foo in the local directory. When the sysem reads it, it sees something like "/tmp/build/bar/pkg/foo" and will look for that path regardless of where it finds the link on the system (e.g. in $pkgdir, in /usr). That's why you must never include "$pkgdir" in the first argument. The link should always point to the installed file, e.g. /usr/lib/foo. The second argument is just the output location where the link will be created. You can add "$pkgdir" to create it directly in $pkgdir, but you could created it anywhere else and move it there later (there's no reason to do more work, but you could). Then there are absolute paths vs relative paths, e.g. "ln -s ../bar foo", which says "wherever you are, go up one directory and then open something called bar". If you move that to a different directory, it will point to a different "bar" (which might not even exist). On the other hand, "ln -s /usr/lib/bar foo" says "wherever you are, go to the root directory, then open "usr", then "lib" and finally "bar". You can move that link anywhere on the system and it will still point to the same target. Back in 1973 when Harry Worthi.... Sorry, that's all the time we have for today's discussion. Join us again next week when Xyne bores you with more knowledge gained from playing with FUSE.

Heiko Baums

10:12 p.m.

New subject: [aur-general] Deletion request

Hi, today I uploaded the package xorriso 0.4.5 to AUR: http://aur.archlinux.org/packages.php?ID=32208 Upstream just told me that it's already included in the package libisoburn from community. So it was nice if someone would delete this package from AUR. Heiko

Ionut Biru

10:15 p.m.

New subject: [aur-general] Deletion request

On 11/25/2009 12:12 AM, Heiko Baums wrote:

...

Hi,

today I uploaded the package xorriso 0.4.5 to AUR: http://aur.archlinux.org/packages.php?ID=32208

Upstream just told me that it's already included in the package libisoburn from community.

So it was nice if someone would delete this package from AUR.

Heiko done

-- Ionut

Heiko Baums

10:26 p.m.

New subject: [aur-general] Deletion request

Am Wed, 25 Nov 2009 00:15:08 +0200 schrieb Ionut Biru :

...

On 11/25/2009 12:12 AM, Heiko Baums wrote:

...
Hi,

today I uploaded the package xorriso 0.4.5 to AUR: http://aur.archlinux.org/packages.php?ID=32208

Upstream just told me that it's already included in the package libisoburn from community.

So it was nice if someone would delete this package from AUR.

Heiko done

Thanks!

Cilyan Olowen

1 Dec 1 Dec

10:03 p.m.

New subject: [aur-general] Deletion request

Please delete jfsrec[1] which is a copy of jfsrec-svn and does not compile. Cilyan [1] http://aur.archlinux.org/packages.php?ID=14090

Ranguvar

11:36 p.m.

New subject: [aur-general] Deletion request

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Tue, Dec 1, 2009 at 17:03, Cilyan Olowen wrote:

...

Please delete jfsrec[1] which is a copy of jfsrec-svn and does not compile. Cilyan

[1] http://aur.archlinux.org/packages.php?ID=14090

So it is. Deleted, thanks. -- Ranguvar [Devin Cofer] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (GNU/Linux) iQIcBAEBCgAGBQJLFah2AAoJEHdXKOHe3MUTEg0P/1Lz3M+K8+/mr/HDZGLqKj4a ItyPkAyxyArWYVABRuuiyDxNE166YrE7jGIu0WqozoTOsevt+rXsRlWHTnIHkDoL p1vwrJvU3wNC518l8W3c9iYum8aCrldfWsbdtaIu59l5iZ4EUytn1SmGOijl+9Cb gdXMZXzZDE/vhN33niPktUqgVlX2M0tUEdf34ppUDZi8HohXQrJSik/Ucj9Rjccw QHBozufp86p15p0SLcF3IKRfpm3iZZjN7Vbkp48inq0ziPBSWNMvQrkxvcGD7VaW hThZhYVGEncjtK5KaqJJL5lqgnxvHr6qEHN0BwIydL3WXzWWztvjUkRAC+TLWKCT 9yzYWg6daOzHvtOskhonOn1FFBpfLrYYqdGmwh3ORDzj7bmmCW+3UtBUSBNyyr9T 5ou2DeCzmOZPrUiwBfm/MqpX7QxuTU9Zyiutru31TwnZzGOk6v92DNF8xec/yYn1 qXxpqGVPdBkcN8TVEmm1+61P+7jAnyvIQ+l/ytR9/pSD6iZMQWhO8H67vmq8WDQA 8d40WxhuayluZDlJZ7es/Z9KH86Nunme9HJDOrr+wsrs8HcviCCyXcXnaxEgK+GE k5rsv5nzF4Gc1rz5t6HxFaXskovTKMrRxjO0ONsjdi9Lc2mc3ujcZnaTKg2tzFY4 gcxH3YzS7zvH24skZbaD =egOV -----END PGP SIGNATURE-----

Daenyth Blank

24 Nov 24 Nov

4:15 a.m.

New subject: [aur-general] How to include sources from sourceforge + creating links not provided by package

On Mon, Nov 23, 2009 at 22:46, Javier Vasquez wrote:

...

Hi,

I'd like to know how to specify sources coming from sorceforge in PKGBUILD, and example could work just fine.

You may or may not be interested in following http://bugs.archlinux.org/task/17093

Allan McRae

4:18 a.m.

New subject: [aur-general] How to include sources from sourceforge + creating links not provided by package

Daenyth Blank wrote:

...

On Mon, Nov 23, 2009 at 22:46, Javier Vasquez wrote:

...
Hi,

I'd like to know how to specify sources coming from sorceforge in PKGBUILD, and example could work just fine.

You may or may not be interested in following http://bugs.archlinux.org/task/17093

Or not given it has absolutely no information... And is that not an "upstream" bug. We close bugs for upstream feature requests in all other packages.

Daenyth Blank

5:34 a.m.

New subject: [aur-general] How to include sources from sourceforge + creating links not provided by package

On Mon, Nov 23, 2009 at 23:18, Allan McRae wrote:

...

Or not given it has absolutely no information...

And is that not an "upstream" bug. We close bugs for upstream feature requests in all other packages.

Given that I _am_ upstream, and I opened the FR...

Allan McRae

5:57 a.m.

New subject: [aur-general] How to include sources from sourceforge + creating links not provided by package

Daenyth Blank wrote:

...

On Mon, Nov 23, 2009 at 23:18, Allan McRae wrote:

...
Or not given it has absolutely no information...

And is that not an "upstream" bug. We close bugs for upstream feature requests in all other packages.

Given that I _am_ upstream, and I opened the FR...

My point was that upstream projects usually have their own bug tracker...

Loui Chang

6:01 a.m.

New subject: [aur-general] How to include sources from sourceforge + creating links not provided by package

On Tue 24 Nov 2009 00:34 -0500, Daenyth Blank wrote:

...

On Mon, Nov 23, 2009 at 23:18, Allan McRae wrote:

...
Or not given it has absolutely no information...

And is that not an "upstream" bug. We close bugs for upstream feature requests in all other packages.

...

Given that I _am_ upstream, and I opened the FR...

He's saying that you shouldn't be using the Arch bug tracker for your own 'personal' projects.

5274

Age (days ago)

5281

Last active (days ago)

List overview

Download

16 comments

11 participants

participants (11)

Allan McRae
Cilyan Olowen
Daenyth Blank
Heiko Baums
Ionut Biru
Javier Vasquez
Laszlo Papp
Loui Chang
Ranguvar
Ray Rashif
Xyne