Package Details: eagle 9.6.2-2

Git Clone URL: https://aur.archlinux.org/eagle.git (read-only, click to copy)
Package Base: eagle
Description: Powerful suite for schematic capture and printed circuit board design (aka eaglecad)
Upstream URL: http://www.autodesk.com/products/eagle
Licenses: custom
Submitter: None
Maintainer: Bevan
Last Packager: Bevan
Votes: 283
Popularity: 0.000091
First Submitted: 2008-03-24 12:05 (UTC)
Last Updated: 2023-08-24 15:16 (UTC)

Pinned Comments

Latest Comments

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 Next › Last »

R00KIE commented on 2012-10-18 13:48 (UTC)

Forgot to say that you don't need to use ln -sf, just ln -s, the target directories should be empty therefore no need to force the creation of the link, does no harm either.

R00KIE commented on 2012-10-18 12:15 (UTC)

I did test my changes before posting the patch and rsync seemed to be working fine, but your use of cp does without that extra dependency so it's better. Here is a new patch [1] with some small modifications. - Keep your usage of cp, however -r is not needed since it is implied by using -a. - Use versioned symlink instead of directory, I suppose the directory should not be versioned, no other package I know of has a directory with version (maybe except python but that is a special case). The symlink could go away with the next version since an update would break any links anyway, after the transition links should not break anymore (if anyone needs it). - Make link for icon in /usr/share/pixmaps and adjust desktop file for that, if you don't want this then you don't need to create the pixmaps directory. - I suppose you don't really need the TryExec line in the desktop file, if the binary is not there, there is some problem with the user's system or the package. - I suppose you don't need the exec inside eagle.sh, it works without it, I don't know how other packages that need scrips do it. - Please consider keeping the line PKGEXT='.pkg.tar', it saves a lot of time when creating the package, if you don't intend to send the package over the internet there is no need to compress it. [1] http://pastebin.com/7YJWpVs7

yuyichao commented on 2012-10-17 21:52 (UTC)

@ROOKIE Yes, I also find having to use ~/eagle annoy. some changes on your patch 1, I use cp instead of rsync, I think it is enough without any additional dependency. 2, I just keep the old versioned directory in /opt and use a symlink for /opt/eagle, just in case someone is expecting the old install path (at least for this version)... (maybe not...) 3, ur use of rsync seems broken(afaik), it will create a subdirectory under .eagle if it exists. plz test, thx for suggestions.

R00KIE commented on 2012-10-17 20:55 (UTC)

Here's a patch that will make eagle behave a bit more like as expected [1], however I don't know how much you will like it. Changes: - No personal lib dir is created, the user can change that later. - Now the bundled libraries show up when the program starts. - No more rm -rf, it just seems to be a bad idea to have rm -rf on a script. - New dependency of rsync, the upside is that it should be faster to start when the version changes and it should leave user added files in place. http://pastebin.com/HgbJUVm1

yuyichao commented on 2012-10-17 16:49 (UTC)

@ROOKIE Well neither the install script nor the startup script creates symlinks in ur home dir afaik... so you shouldn't have the problem with this package... Copying everything every time doesn't sound like a good idea for me either, but since eagle is really doing sth weird (looking for sth systemwide in user directory..... as well as write to this dir) it is a little tricky to do symlinks.... (not hard but basically I cannot simply symlink the directory as a whole) need to find time to do that. And AFAIK it is eagle's install script that installs the package with the version suffix... so now I will just symlink /opt/eagle to /opt/eagle-$pkgver, hopefully that can help you if u r doing ur own trick. suggestions/patches welcome.

R00KIE commented on 2012-10-17 14:26 (UTC)

Could you install into /opt/eagle/ instead of /opt/eagle-$pkgver? Since by default eagle looks for libraries in ~/eagle/lbr, symlinking the libraries in /opt/eagle-$pkgver/lbr into ~/eagle/lbr will break with every update. Changing the configuration to look for libraries in /opt/eagle-$pkgver/lbr will prevent the user from using personal libraries and copying the libraries in /opt/eagle-$pkgver/lbr into ~/eagle/lbr is also not a good idea because the user would not notice if any library gets updated in the package.

yuyichao commented on 2012-10-10 16:36 (UTC)

@swiftgeek well it actually does depend on gcc-libs (you can see this by ldd) although the correct dependency for x86_64 is lib32-gcc-libs (binary for x86) rather than gcc-libs-multilibs (binary for x86_64). Not really sure if it is a direct dependency or pulled in by one of other dependencies (too lazy to check), but since it was here before I will just change the package name rather than remove it. will soon correct it.

swiftgeek commented on 2012-10-10 16:21 (UTC)

@nboichat: Nothing is building here -.-

swiftgeek commented on 2012-10-10 16:21 (UTC)

gcc-libs-multilib is NOT needed. Having it installed triggers bugs in eagle!

pernix commented on 2012-10-10 11:03 (UTC)

md5sum for eagle 6.3.0 x86_64: 661defb4ae9531e829a96c9aaaa16b0e

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 Next › Last »