Bug 398781 – sci-electronics/eagle-6.1.0 ebuild bump

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description Thomas Axelsson 2012-01-13 16:32:04 UTC]

The directory structures seemed identical so I updated the eagle-5.11.0 ebuild
and it seems to work nicely. Updated the version numbers in the text (formats are incompatible this time to, binary -> xml).

I'm a bit unsure about the dependencies. The oldest available emul-lib in
portage seems to contain the needed versions of the deps. I haven't looked
closely at the x86 deps.

It needs the eagle_wrapper_script from the files directory already in portage.

This release, among other things, fixes the CAM processor bug in eagle-6.0.0.

Reproducible: Always

[Comment 1 Thomas Axelsson 2012-01-13 16:32:45 UTC]

Created attachment 298855 [details]
Ebuild for eagle-6.0.0. Needs files/eagle_wrapper_script from previous  versions.

[Comment 2 Thomas Axelsson 2012-01-13 16:34:09 UTC]

Created attachment 298857 [details]
Ebuild for eagle-6.1.0. Needs files/eagle_wrapper_script from previous  versions.

Ebuild is actually for eagle-6.1.0. Replaced attachment with correct description.

[Comment 3 Maciej Grela 2012-02-01 23:17:23 UTC]

Created attachment 300731 [details]
An updated ebuild for sci-electronics/eagle-6.1.0

Hi,

I also wrote an ebuild for sci-electronics/eagle-6.1.0 with the following improvements from eagle-5 ebuild:

1. Updated the list of docs that can be installed, made the docs handling cleaner and easier to understand.
2. Used the make_wrapper function to generate the eagle wrapper instead of shipping a wrapper script in ${FILESDIR}
3. Added handling for the 'zh' language.

I also removed the fix adding XLIB_SKIP_ARGB_VISUALS=1 to the wrapper script. The FAQ entry describing this: http://www.cadsoftusa.com/training/faq/#17040701 points to an ancient bug from 2006 and I couldn't reproduce it under Gnome-3.0 in a recent system.

Please consider the bump request.

[Comment 4 Christian Ruppert (idl0r) 2012-04-04 12:40:59 UTC]

*** This bug has been marked as a duplicate of bug 397491 ***