There are no bugs logged at bugzilla and I guess that I'm not the only one using this piece of software so it should be safe to mark as stable. Reproducible: Always
As of today it's been 30 days since I checked in the ebuild. Arch teams, can you stabilize please?
Stable on x86 And no, you're not the only one using it Alex ;)
AMD64: compiles. Runs, but when the menus at the top are opened their names all change to 'Help' (they start off as file/view/option/window as normal). The main menu tree also does not behave properly. There are other various graphical artefacts in the program which essentially make it unusable. Could another AMD64 dev/AT confirm this pls? Portage 2.1.2.12 (default-linux/amd64/2007.0/desktop, gcc-4.1.2, glibc-2.5-r4, 2.6.22-gentoo-r5 x86_64) ================================================================= System uname: 2.6.22-gentoo-r5 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ Gentoo Base System release 1.12.9 Timestamp of tree: Thu, 30 Aug 2007 16:50:01 +0000 app-shells/bash: 3.2_p17 dev-java/java-config: 1.3.7, 2.0.33-r1 dev-lang/python: 2.4.4-r4 dev-python/pycrypto: 2.0.1-r6 sys-apps/baselayout: 1.12.9-r2 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.24 virtual/os-headers: 2.6.21 ACCEPT_KEYWORDS="amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=athlon64 -O2 -msse3 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/X11/xkb" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-march=athlon64 -O2 -msse3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="buildpkg collision-protect distlocks fixpackages metadata-transfer multilib-strict sandbox sfperms strict test userpriv" GENTOO_MIRRORS="http://gentoo.virginmedia.com http://distfiles.gentoo.org" LINGUAS="en en_GB" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/portage/local/layman/enlightenment /usr/portage/local" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="3dnow X Xaw3d a52 aac acpi alsa amd64 audiofile berkdb bitmap-fonts branding bzip2 cairo caps cddb cdparanoia cdr cli cracklib cups curl dbus dri dvd dvdr dvdread emboss encode evo exif expat fam ffmpeg firefox foomaticdb gdbm gif glitz gs gtk guile hal iconv icu imagemagick imlib isdnlog ithreads java javascript jpeg libsamplerate libwww lirc lm_sensors logrotate mad midi mmap mmx mmxext mp3 msn mudflap ncurses nls nptl nptlonly nsplugin offensive ogg openal opengl openmp pam pango pcre pdf perl png ppds pppd python qt3support readline reflection sdl session sndfile spl sse sse2 ssl startup-notification svg symlink tcl tcpd test threads tiff tk truetype truetype-fonts type1-fonts unicode usb v4l v4l2 vorbis wifi x264 xcb xine xml xorg xosd xpm xscreensaver xv zlib" ALSA_CARDS="usb-audio" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en en_GB" LIRC_DEVICES="mceusb2" USERLAND="GNU" VIDEO_CARDS="nvidia" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Update: apparently this is due to eagle not liking the Composite extension
AMD64: works, as far as I can test with the free mode & no hardware. Might be worth putting a note into the ebuild about not working with the composite extension, since that'll be more and more popular in the future?
The ugliness! I could stabilize it on amd64, since anyone using this program has to be from the stone age of X and doesn't use Composite anyway. But it would be nice if you add a note to the ebuild about the Comp issue first. (and let upstream know or fix the issue)
See http://www.cadsoft.de/faq.htm#17040701 for related info, I think. This issue seems to be resolved by creating their suggested script: #!/bin/bash export XLIB_SKIP_ARGB_VISUALS=1 /opt/eagle/bin/eagle ---- Is it appropriate to create this shell script as part of installation? What naming sequence can I follow?
(In reply to comment #7) > See http://www.cadsoft.de/faq.htm#17040701 for related info, I think. > > This issue seems to be resolved by creating their suggested script: > > #!/bin/bash > > export XLIB_SKIP_ARGB_VISUALS=1 > /opt/eagle/bin/eagle > > ---- > Is it appropriate to create this shell script as part of installation? What > naming sequence can I follow? > Yes, it does work faster on rendering! (x86) Thanks Joe!
(In reply to comment #7) > Is it appropriate to create this shell script as part of installation? What > naming sequence can I follow? For users, it would be least disruptive to install the binary to another directory (libexec) and replace the /usr/bin/eagle by the script.
I agree with the idea of a shell script. Maybe this caller script can set some more variables, so that /etc/env.d/90eagle script could be removed? The eagle binary is already at /opt/eagle/bin/eagle. The script could be placed at /usr/bin/eagle
I still have to look into what $ROOTPATH is actually used for, but certainly the addition to $PATH will be removed. The env.d entry is still needed for prelink; see bug #191961.
I accidentally unkeyworded it with my last update, but it's fixed now. Thanks all and keep on testing -r1.
I'm commenting here just to avoid opening another bug. I saw that the -r1 ebuild creates a shell script wrapper. However, any parameters passed to the script are not passed to the binary. The solution is simple, just replace this line: echo "${INSTALLDIR}/bin/eagle" >> "${D}/usr/bin/eagle" with this: echo "${INSTALLDIR}/bin/eagle" '"$@"' >> "${D}/usr/bin/eagle"
(In reply to comment #13) > I'm commenting here just to avoid opening another bug. I saw that the -r1 > ebuild creates a shell script wrapper. However, any parameters passed to the > script are not passed to the binary. The solution is simple, just replace this > line: > echo "${INSTALLDIR}/bin/eagle" >> "${D}/usr/bin/eagle" > with this: > echo "${INSTALLDIR}/bin/eagle" '"$@"' >> "${D}/usr/bin/eagle" > Thanks. It'll be fixed in -r2 and in CVS soon.
