http://www.xaraxtreme.org/developers/sourcecode.html The source version of Xara Xtreme (a vector and bitmap graphics editor) for Linux (aka Xara LX) was released a few days ago... (binary versions were already available, here: http://www.xaraxtreme.org/download/) I asked a few questions about the source code archive in http://www.talkgraphics.com/showthread.php?t=20579 (official forum), as there are a few problems with the way it is now... (about the GPL, the wxWindows dependency (x11-libs/wxGTK on gentoo) and the fact the source code archive does not contain a version number nor a date...) Another problem is that it does not work for me ^_^" but I don't have enough time to investigate... Anyway, it would be nice to provide ebuilds for this package (and/or for the binary version), even if it is, indeed, still in development... or at least to provide ebuilds here, to prepare for a more stable version, if no one want to maintain the package, for now... The ebuild should go to the media-gfx category, like every graphics editors... but the ebuild might be rename to something else... The official global name for the product is "Xara Xtreme", but the Linux version sometimes is referred to as "Xara LX"... (but not always). Still, "Xara Xtreme" is the most common name used for the product, so I guess the ebuild should be named "xara-xtreme"...
Created attachment 82616 [details] New package: media-gfx/xara-xtreme-20060319 I'm not sure about the dependencies... some are listed here: http://www.xaraxtreme.org/developers/documentation/xara_lx_linux_build_instructions.html but versions are not always given, and I still don't have much experience in setting the dependencies... There also is a problem with wxGTK, as stated in the build instructions (link above), as they used a CVS version... I guess the best would be to wait for the next stable version of wxGTK... (2.6.3).
http://www.xaraxtreme.org/developers/sourcecode.html According to this, the versions are: 0.3.676 and 0.3.689. :) That is the official homepage of the sourcecode. ;) One is considered a stable build and the other a testing build. :) So, one ebuild for ARCH and the other for ~ARCH. :P Cheers.
Created attachment 82618 [details] Test ebuild for the CVS version of wxGTK (20060303) A test ebuild for the CVS version of wxGTK, as http://www.xaraxtreme.org/developers/documentation/xara_lx_linux_build_instructions.html states wxWidgets (wxGTK under Gentoo) 2.6.2 is not enough... I used the 2.6.2-r1 ebuild, changed the SRC_URI and S variables and commented the "epatch ${FILESDIR}/intl.cpp.diff" line, as the patch does not apply properly (I didn't try to find why).
(In reply to comment #1) > Created an attachment (id=82616) [edit] > New package: media-gfx/xara-xtreme-20060319 > > I'm not sure about the dependencies... some are listed here: > http://www.xaraxtreme.org/developers/documentation/xara_lx_linux_build_instructions.html > but versions are not always given, and I still don't have much experience in > setting the dependencies... > > There also is a problem with wxGTK, as stated in the build instructions (link > above), as they used a CVS version... I guess the best would be to wait for the > next stable version of wxGTK... (2.6.3). > I guess this would the the CVS version, and the ones I mentioned the released versions? The Download URLS for the ones I mentioned are: http://downloads.xara.com/opensource/RecXaraLX0.3_rev676.tar.bz2 http://downloads.xara.com/opensource/XaraLX0.3_rev689.tar.bz2 Is the link you gave updated daily?
(In reply to comment #2) > http://www.xaraxtreme.org/developers/sourcecode.html > According to this, the versions are: > 0.3.676 and 0.3.689. :) That is the official homepage of the sourcecode. ;) One > is considered a stable build and the other a testing build. :) So, one ebuild > for ARCH and the other for ~ARCH. :P > You should look again ^_^ The link you gave is indeed the link to the source version, as stated in my original report, but there are no mention to the versions you list... these versions are the binary versions, listed at http://www.xaraxtreme.org/download/ (link which I also gave in my original report). In the last link, they say "This is NOT a fully working drawing program yet. It demonstrates work in progress. However most of the important drawing tools are now working well, so it's now at the point where adding save and export capability it will actually make it useful!", so it's nowhere near "stable" :) (well, I should have read twice too, as I didn't know it was that much in heavy development...) I guess a "_alpha" suffix should be added to the ebuild version :) (In reply to comment #4) > > The Download URLS for the ones I mentioned are: [...] > Try to download the files, they *are* binary versions ;) > > Is the link you gave updated daily? > I don't know how often the http://www.xaraxtreme.org/downloads/XaraLX.tar.bz2 package is updated... (I asked on their forum to add a version number or a date). At the bottom of http://www.xaraxtreme.org/developers/sourcecode.html it says a binary version is built every day, based on the most recent source code... so maybe they do update the source code archive every day...
(In reply to comment #5) > You should look again ^_^ The link you gave is indeed the link to the source > version, as stated in my original report, but there are no mention to the > versions you list... these versions are the binary versions, listed at > http://www.xaraxtreme.org/download/ (link which I also gave in my original > report). > > In the last link, they say "This is NOT a fully working drawing program yet. It > demonstrates work in progress. However most of the important drawing tools are > now working well, so it's now at the point where adding save and export > capability it will actually make it useful!", so it's nowhere near "stable" :) > (well, I should have read twice too, as I didn't know it was that much in heavy > development...) > > I guess a "_alpha" suffix should be added to the ebuild version :) > > > > Try to download the files, they *are* binary versions ;) > > > > > I don't know how often the http://www.xaraxtreme.org/downloads/XaraLX.tar.bz2 > package is updated... (I asked on their forum to add a version number or a > date). > > At the bottom of http://www.xaraxtreme.org/developers/sourcecode.html it says a > binary version is built every day, based on the most recent source code... so > maybe they do update the source code archive every day... > Indeed. Their website is confusing. <_< And that is suppose to be a professional group too. -_-' Ah well.
seems really interesting
Created attachment 82672 [details] Ebuild for wxGTK-2.6.3_rc2, needed by xara-xtreme This time, I used the official package, instead of the CVS snapshot from the Xara website... From the 2.6.2-r1 ebuild, I added the MY_PV and MY_PV_BARE variables, to store returns values from the versionator functions (inherited in the build), and I used them in the SRC_URI and S variables...
(In reply to comment #0) > > I asked a few questions about the source code archive in > http://www.talkgraphics.com/showthread.php?t=20579 (official forum), as there > are a few problems with the way it is now... (about the GPL, the wxWindows > dependency (x11-libs/wxGTK on gentoo) and the fact the source code archive > does not contain a version number nor a date...) > They answered: - that the "COPYING" file, which stated the project was still proprietary, is to be ignored... (the "LICENCE" file already states the project is licenced under the GPL-2; - that wxWidgets (wxGTK under Gentoo), version >2.6.2 is required... (see the wxGTK-2.6.3_rc2 ebuild, in this report attachments). ... and they modified the filename of the source code archive to include a version number. About the licence, in the "libs" directory, the "LIBS-LICENSE" file states the "libCDraw.a" library (binary), still is not GPL-2... The temporary licence states we can only distribute the library with the Xara Extreme source code or binary version... I guess this one is not an error, so we'll have to at least tell it to the user...
Created attachment 82745 [details] New package: media-gfx/xara-xtreme-0.3_alpha693 ebuild As Xara changed the filename of the source code archive and updated the file, here is the new ebuild.
Created attachment 82779 [details] New package: media-gfx/xara-xtreme-0.3_alpha693 ebuild Corrected the dependency for wxGTK (">=x11-libs/wxGTK-2.6.3_rc2", instead of version >=2.6.2) and added a "debug" USE flag.
This app is awesome. can't wait to have it in portage!
Created attachment 83038 [details] media-gfx/xara-xtreme-0.3_alpha713 ebuild Bumped version to alpha 713 and modified the einfo about the license, as it is a bit more complex than what I thought... (they give additional rights).
Created attachment 83190 [details] New version with dependencies updated and a patch for wxGTK dependencies This version added a dependency on dev-util/cvs, since it won't compile without it. It also applies a patch to the configure.in so that the application is compiled when wxGTK-2.4 and 2.6 are installed on the same system (they are slotted)
Created attachment 83191 [details, diff] patch for when wxGTK-2.4 and 2.6 are installed in the system
Can someone check the ebuilds I just proposed and tell me if they are working fine? I find it strange that I have very little files installed and a warning when I launch the application.
Created attachment 83213 [details] xara-xtreme-9999.ebuild this is svn xara ebuild version
Created attachment 83580 [details] media-gfx/xara-xtreme-0.3_alpha752.ebuild Version bump and some cleaning... For those who had the problem with the "No handler found" error message, when starting Xara, it has been fixed (I don't know since when exactly, but it is in this version).
Comment on attachment 82672 [details] Ebuild for wxGTK-2.6.3_rc2, needed by xara-xtreme wxGTK-2.6.3 (final version) has been released a few days ago... An ebuild is available here: https://bugs.gentoo.org/show_bug.cgi?id=127734 (probably soon be in Portage).
Is this ready for 64 bit yet? It wont compile for me using the alpha752 ebuild with wxGTK 2.6.3 and the wxgtk patch. I'll attach the build log.
Created attachment 83691 [details] Emerge log of failed compile on amd64
(In reply to comment #20) > Is this ready for 64 bit yet? It wont compile for me using the alpha752 ebuild > with wxGTK 2.6.3 and the wxgtk patch. I'll attach the build log. > From your log: ################################################################ checking wxWidgets version... 2.6.3 Warning: No config found to match: /usr/bin/wx-config-2.6 --static=no --debug=no --unicode=yes --cppflags in /usr/lib64/wx/config If you require this configuration, please install the desired library build. If this is part of an automated configuration test and no other errors occur, you may safely ignore it. You may use wx-config --list to see all configs available in the default prefix. Warning: No config found to match: /usr/bin/wx-config-2.6 --static=no --debug=no --unicode=yes --cxxflags in /usr/lib64/wx/config If you require this configuration, please install the desired library build. If this is part of an automated configuration test and no other errors occur, you may safely ignore it. You may use wx-config --list to see all configs available in the default prefix. Warning: No config found to match: /usr/bin/wx-config-2.6 --static=no --debug=no --unicode=yes --libs in /usr/lib64/wx/config If you require this configuration, please install the desired library build. If this is part of an automated configuration test and no other errors occur, you may safely ignore it. You may use wx-config --list to see all configs available in the default prefix. checking wxWidgets GTK usage... not found ./configure: line 22066: FT_CFLAGS: command not found ./configure: line 22067: PANGO_CFLAGS: command not found ################################################################ Running `wx-config-2.6 --static=no --debug=no --unicode=yes --cppflags` I get: -I/usr/lib/wx/include/gtk2-unicode-release-2.6 -I/usr/include/wx-2.6 -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1 -DNO_GCC_PRAGMA If it returns nothing like this for you, I guess the first problem is related to wxGTK... Then, there is some note about the AMD64 architecture, on the Xara website: http://www.xaraxtreme.org/download/ (the "Installation Instructions on Linux AMD64" chapter). It is for the binary version, but I guess it applies to the source code version too... If it still does not work, on this page: http://www.xaraxtreme.org/developers/documentation/xara_lx_linux_build_instructions.html it is written: "XaraLX on Linux is currently only known to build on x86 and x86-64 architectures. We hope to support further Linux architectures later.", so you might try to fill a bug report at http://bugzilla.xara.com/ I don't know much about the 64 bits architecture, so I can't do more.
Thanks for your help. The commands listed failed with --unicode=yes and worked with --unicode=no. Looks like it requires wxGTK to be built with unicode support which I had not. Recompiling now...will post results.
Recompiling wxGTK with unicode did the trick. Can we put in a unicode use flag, or if unicode is required, check to see that wxGTK is built with unicode support? This can also be marked ~amd64.
(In reply to comment #24) > Recompiling wxGTK with unicode did the trick. Can we put in a unicode use > flag, or if unicode is required, check to see that wxGTK is built with unicode > support? This can also be marked ~amd64. > There is already someone asking about it, in the wxGTK-2.6.3 ebuild discussions, here: bug #127734 ... but seeing the ebuild ("[...] configure_build [...] unicode [...]"), and my built logs, wgGTK is always built with unicode support... Search your wxGTK built log for "unicode"... you'll see it is first built without Unicode support, then with Unicode support... (See bug #112073 -the answers, not the original report-, for more informations). If wxGTK is not built two times, without and with unicode support, maybe there is a problem with the AMD64 architecture... Try to search for already existing bug reports or forum threads about it... if there's nothing, maybe you should comment on bug #127734 about it (or fill a new but report if it happens with previous versions, -already in Portage-, too -but there's already multiple invalid bugs about it, so be sure to triple-check everything ^_^). About marking the xara-xtreme ebuild ~amd64, did you have to follow the instructions from http://www.xaraxtreme.org/download/ (the "Installation Instructions on Linux AMD64" chapter), which I mentioned in comment #22, or not?
All I had to do to get xara-xtreme installed on amd64 was: download the ebuild for wxGTK 2.6.3, add unicode to package.use (It does have a working unicode useflag, which I have disabled by default. so it needed this to work with xara.) I used the most recent available ebuild for xara posted here (alpha752) along with the patch for having wxGTK 2.4/2.6 installed on same system. Everything from there worked out the door. The special instructions listed at the xara-xtreme seem to be for getting the 32bit compiled binary running on a 64 bit system (a-la-emul-libs..) as far as I can tell. Which doesn't apply to this ebuild.
Created attachment 83789 [details] media-gfx/xara-xtreme-0.3_alpha759.ebuild Version bump and marking the ebuild ~amd64 (Note I didn't test the ebuild and won't update the report myself, as of now, as I should better concentrate on my work ^_^")
xara-xtreme-0.3_alpha759 worked great for me on amd64.
(In reply to comment #17) > Created an attachment (id=83213) [edit] > xara-xtreme-9999.ebuild > > this is svn xara ebuild version > Im using xara-xtreme-9999.ebuild for daily snapshot compilling, but I also have slotted older version of wxgtk (wxGTK-2.4.2-r4 required by audacity) Im unable to compile xara, until manually: cd /rm wx-config rm wx-config ln -s wx-config-2.6 wx-config .. after that, xara snapshot compiles succefully
typo, of course: cd /usr/bin/ ...
Created attachment 84600 [details] Ebuild for the latest stable version of XaraLX as of April 11 Here is an updated version of the ebuild that is for the latest "stable" version of XaraLX as of April 11, 2006. The ebuild is based on xara-xtreme-0.3_alpha759.ebuild with a name change to match the source filename as well as some added dependencies to match what the website lists as prereqs to building XaraLX -Jon
Created attachment 84736 [details] XaraLX-0.4_alpha798.ebuild
Created attachment 84737 [details, diff] New version of the patch for systems who have the wxGTK-2.4 and wxGTK-2.6 installed
seems mature to go in portage cvs.
Created attachment 84744 [details] XaraLX-0.4_alpha798.ebuild Here is an updated version of the ebuild for version 0.4r798 that has the dependency for md5sum added along with a check to make sure that wxGTK has been built with unicode support -Jon
Created attachment 85597 [details] xara-0.4.876.ebuild New ebuild, without the patch but using the wxwidgets eclass instead. Xara seems rather unready to go stable at any time. Many bugs need to be fixed upstream. I am considering taking up maintainership, though.
Forgot to CC myself. Sorry for the bugspam.
(In reply to comment #37) > Forgot to CC myself. Sorry for the bugspam. > No need to add a comment for this ^_^" If you just add yourself to the CC list, people can configure their Bugzilla account to not receive this change... but if you add a comment, most people will receive it :) About your ebuild, I don't think it should be named just "xara"... Xara is a firm which produces multiple other pieces of software. As said in my original report, "xara-xtreme" seems to be the best name for the package. "xara-lx" is another possibility, but the code is under the GPL, so there probably will be at least xBSD, MacOS and Solaris ports... (probably even more, as the product becomes more popular), so "lx" (from "Linux"), is too restrictive... About the package description, I think we should stick to more neutral terms ^_^" "venerable" does not mean much for a software package ^_^" And "GPL" should probably only be added in a short description if the product is available *on the same OS* (like unrar), in a non-GPL version, which is not the case for Xara Xtreme. I think at least "vector" and "bitmap" (or derivatives) should appear in the short description, with "graphics" or "image", for quick and easy searching. Why did you add an "unicode" USE flag? It does not seem to be used in the ebuild/eclasses... Well, nothing urgent, as, as you said, the package is far from stable :) Thanx for considering to maintain this package :) Do you think it might go into Portage as alpha software? (hard masked, with "alpha" temporarily added to the package name or to the description). It would help people follow the development progress, on a regular basis, more easily :) (no need to check the report and manually download and prepare the ebuild).
(In reply to comment #38) > About your ebuild, I don't think it should be named just "xara"... Xara is a > firm which produces multiple other pieces of software. As said in my original > report, "xara-xtreme" seems to be the best name for the package. "xara-lx" is > another possibility, but the code is under the GPL, so there probably will be > at least xBSD, MacOS and Solaris ports... (probably even more, as the product > becomes more popular), so "lx" (from "Linux"), is too restrictive... I didn't really call it anything yet. I think it ought to be media-gfx/xara-xtreme, though. > About the package description, I think we should stick to more neutral terms > ^_^" "venerable" does not mean much for a software package ^_^" And "GPL" > should probably only be added in a short description if the product is > available *on the same OS* (like unrar), in a non-GPL version, which is not the > case for Xara Xtreme. I think at least "vector" and "bitmap" (or derivatives) > should appear in the short description, with "graphics" or "image", for quick > and easy searching. My basic idea was to fix the ebuild first. I am more concerned about building and installing properly, including stuff like setting the right keywords, than about the Gentoo package name or the package description. :) > Why did you add an "unicode" USE flag? It does not seem to be used in the > ebuild/eclasses... It's used in pkg_setup. > Well, nothing urgent, as, as you said, the package is far from stable :) It's rather easy to make it segfault, indeed. And all the menu options labeled "Unimplemented" are no help either. > Thanx for considering to maintain this package :) Do you think it might go into > Portage as alpha software? (hard masked, with "alpha" temporarily added to the > package name or to the description). It would help people follow the > development progress, on a regular basis, more easily :) (no need to check the > report and manually download and prepare the ebuild). That would mean adding more and more ebuilds to keep up with the huge number of builds churned out on a weekly basis, which is hardly useful. Shortly after I posted my ebuild, for example, I noticed yet another build on the website with no mention of any changes since the last one (the new one builds though). I am currently waiting until development on Xara settles down and most features are implemented/ported and most of the current bugs are fixed. I certainly don't want bugs.g.o/my Gentoo mailbox to get flooded with bug reports for this yet, so I'm not going to put it in portage straight away. Some other dev might want to, though. For now let's keep this bug open to gather more input from devs and users.
> (In reply to comment #39) > > [About the ebuild name and description] > Ok. As there were already another name and description for/in the previous ebuilds, I just thought you wanted to change them. > > It's used in pkg_setup. > Not in the ebuild you posted ^_^" (the check about wxGTK does not depend on the "unicode" USE flag being set for the Xara Xtreme package). And if you wanted to check that wxGTK had been built with the "unicode" USE flag, only if the "unicode" flag was set for the Xara Xtreme ebuild, are you sure Unicode is not a strict requirement of Xara Xtreme? Xara says: "Xara LX uses the Unicode version of the library [wxGTK] [...], this means that these options must be specified on the configure command line." (http://www.xaraxtreme.org/developers/documentation/xara_lx_linux_build_instructions.html) I never tried without; maybe it's just used when you use another language for the UI than English... (in which case, the "nls" USE flag should trigger the check, not the "unicode" USE flag). > > I am currently waiting until development on Xara settles down > and most features are implemented/ported and most of the current > bugs are fixed. > Ok, I'll wait then :) (not that I have much time to test it regularly anyway, but I'm really interested in the future of this program)
Created attachment 86291 [details] XaraLX-0.4.967.ebuild This is an updated version of the ebuild with added dependencies to match the Xara website: http://www.xaraxtreme.org/developers/documentation/xara_lx_linux_build_instructions.html I also put the dependency on dev-util/cvs back in since Xara will not build without cvs installed. In my brief testing to make sure it worked I noticed that save and open functionality has been added to this version of XaraLX
0.4.967 worked fine for me on amd64 after having added ~amd64 keyword to the ebuild.
Important to note is that XaraLX's license is currently not strictly GPL. In the libs subdirectory of the build tree sits an additional license, i.e. xara-0.5.1147/work/XaraLX-0.5r1147/libs/LIBS-LICENSE "TEMPORARY LICENSE FOR CDRAW", pertaining to libCDraw, which is only included in binary form for a limited number of architectures. Under 1.a, this license seems to indicate that we may not distribute XaraLX's source code including the CDraw libraries, but only such packages that contain a XaraLX binary as well.
(In reply to comment #43) > Important to note is that XaraLX's license is currently not strictly GPL. In > the libs subdirectory of the build tree sits an additional license, i.e. > > xara-0.5.1147/work/XaraLX-0.5r1147/libs/LIBS-LICENSE > > "TEMPORARY LICENSE FOR CDRAW", pertaining to libCDraw, which is only included > in binary form for a limited number of architectures. Under 1.a, this license > seems to indicate that we may not distribute XaraLX's source code including the > CDraw libraries, but only such packages that contain a XaraLX binary as well. > See comment #9 :) They say: "[...] the intent of this license is to say that if you distribute the libraries, you must either do it with a XaraLX executable, or with the source itself (if you don't want to do this, please just refer people to our web site where they can download the libraries); and you are only allowed to use the libraries with the GPL version of XaraLX" So there is no problem with distributing the source code in Portage, to build Xara Xtreme. About paragraph 1.a... well, read 1.b ;) (anyway, this is to forbid distribution of the Cdraw libraries without Xara Xtreme, so it does not apply here...) The problem is that we have to tell the user that Xara Xtreme still uses a precompiled version of the CDraw library... it was written in some ebuilds (https://bugs.gentoo.org/attachment.cgi?id=84744), but not in some others... this is an important warning, for users who'd like to avoid non-free stuffs (well, this is only a temporary issue, and this should be clear, in the warning). For people wanting to modify Xara Xtreme and distribute a modified version, I guess they will anyway find the problem with the CDraw libraries, but a warning in the ebuild still is useful.
(In reply to comment #44) > (In reply to comment #43) > > Important to note is that XaraLX's license is currently not strictly GPL. In > > the libs subdirectory of the build tree sits an additional license, i.e. > > > > xara-0.5.1147/work/XaraLX-0.5r1147/libs/LIBS-LICENSE > > > > "TEMPORARY LICENSE FOR CDRAW", pertaining to libCDraw, which is only included > > in binary form for a limited number of architectures. Under 1.a, this license > > seems to indicate that we may not distribute XaraLX's source code including the > > CDraw libraries, but only such packages that contain a XaraLX binary as well. Seem to have dropped an entire paragraph there. 8-) > See comment #9 :) > > They say: "[...] the intent of this license is to say that if you distribute > the libraries, you must either do it with a XaraLX executable, or with the > source itself (if you don't want to do this, please just refer people to our > web site where they can download the libraries); and you are only allowed to > use the libraries with the GPL version of XaraLX" > > So there is no problem with distributing the source code in Portage, to build > Xara Xtreme. The problem is not with this LIBS-LICENSE, but with the LICENSE file, which refers to a file called 'GPL' and the WXXTRA-LICENSE as well as LIBS-LICENSE. The WXXTRA-LICENSE appears to be the 3.1 version of portage/licenses/wxWinLL-3, which would need to be added. The LIBS-LICENSE would need to be committed to Portage separately, as well as the LICENSE file. Apart from these trivial matters, there's the more important matter of the GPL. Basically, distributing part of XaraLX as GPL and part as wxWindows-3.1 and yet another part (CDraw) under yet another license is simply not permitted under the GPL. For one thing, you cannot just inject a binary only library and then say that the GPL applies to the entire work except when it does not, and for another, it's probably worht waiting for XaraLX to be licensed entirely under GPL. > > About paragraph 1.a... well, read 1.b ;) (anyway, this is to forbid > distribution of the Cdraw libraries without Xara Xtreme, so it does not apply > here...) Which is yet another breach of the GPL. > The problem is that we have to tell the user that Xara Xtreme still uses a > precompiled version of the CDraw library... it was written in some ebuilds > (https://bugs.gentoo.org/attachment.cgi?id=84744), but not in some others... > this is an important warning, for users who'd like to avoid non-free stuffs > (well, this is only a temporary issue, and this should be clear, in the > warning). For people wanting to modify Xara Xtreme and distribute a modified > version, I guess they will anyway find the problem with the CDraw libraries, > but a warning in the ebuild still is useful. That's the trivial matter I discussed earlier in this comment in my reconstruction of the lost paragraph. Adding a license is trivial, i.e. committing the ./LICENSE file as portage/licenses/XaraLX or some such, as well as the wxWindows 3.1 license. The problem is that XaraLX claims the source code is GPL when, by their own terms, it is clearly not. Until XaraLX is released under an unproblematic license, and until the avalanche of builds dies down (probably near a 1.0 release, the way it's going now), it's hardly worth investing time in Gentoo ebuilds, IMHO, however promising the project may be. I'm closing this bug for now. Please feel free to reopen it when XaraLX is (nearly) ready.
(In reply to comment #41) > Created an attachment (id=86291) [edit] > XaraLX-0.4.967.ebuild > > This is an updated version of the ebuild with added dependencies to match the > Xara website: > http://www.xaraxtreme.org/developers/documentation/xara_lx_linux_build_instructions.html > > I also put the dependency on dev-util/cvs back in since Xara will not build > without cvs installed. > > In my brief testing to make sure it worked I noticed that save and open > functionality has been added to this version of XaraLX > I have tried this ebuild also for version 0.5.1197 and 0.5.1203, but it didn't work: Testing for new resources and svn version Rebuilding svn version svn: '..' is not a working copy Writing svnversion.h Rebuilding resources - new checksum 496d1c122765b0f6f2275a5675744bd4 .././wxOil/xrc/EN/aboutres.xrc:23 Warning: Bitmap ./xrc/2.png not found .././wxOil/xrc/EN/aboutres.xrc:82 Warning: Bitmap ./xrc/2.png not found .././wxOil/xrc/EN/aboutres.xrc:149 Warning: Bitmap ./xrc/2.png not found .././wxOil/xrc/EN/aboutrsw.xrc:23 Warning: Bitmap ./xrc/2.png not found .././wxOil/xrc/EN/barsdlgs.xrc:752 Warning: Bitmap ./xrc/leftbrace.png not found .././wxOil/xrc/EN/barsdlgs.xrc:756 Warning: Bitmap ./xrc/rightbrace.png not found .././wxOil/xrc/EN/barsdlgs.xrc:760 Warning: Bitmap ./xrc/label.png not found .././wxOil/xrc/EN/errordlg.xrc:31 Warning: Bitmap ./xrc/.png not found .././wxOil/xrc/EN/register.xrc:19 Warning: Bitmap ./xrc/2.png not found .././wxOil/xrc/EN/textres.xrc:26 Warning: Bitmap ./xrc/aspect.png not found .././wxOil/xrc/EN/textres.xrc:74 Warning: Bitmap ./xrc/tracking.png not found .././wxOil/xrc/EN/textres.xrc:78 Warning: Bitmap ./xrc/kerning.png not found .././wxOil/xrc/EN/camelot.xrc:7 Warning ID_FILE_NEW multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:244 Previous definition here .././wxOil/xrc/EN/camelot.xrc:11 Warning wxID_OPEN multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:250 Previous definition here .././wxOil/xrc/EN/camelot.xrc:16 Warning wxID_PRINT_SETUP multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:274 Previous definition here .././wxOil/xrc/EN/camelot.xrc:21 Warning ID_FILE_MRU_FILE1 multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:220 Previous definition here .././wxOil/xrc/EN/camelot.xrc:26 Warning wxID_EXIT multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:124 Previous definition here .././wxOil/xrc/EN/camelot.xrc:33 Warning ID_VIEW_TOOLBAR multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:382 Previous definition here .././wxOil/xrc/EN/camelot.xrc:37 Warning ID_VIEW_STATUS_BAR multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:376 Previous definition here .././wxOil/xrc/EN/camelot.xrc:44 Warning ID_HELP_INDEX multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:298 Previous definition here .././wxOil/xrc/EN/camelot.xrc:48 Warning ID_HELP_USING multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:304 Previous definition here .././wxOil/xrc/EN/camelot.xrc:53 Warning wxID_ABOUT multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:118 Previous definition here .././wxOil/xrc/EN/camelot.xrc:62 Warning ID_FILE_NEW multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:244 Previous definition here .././wxOil/xrc/EN/camelot.xrc:66 Warning wxID_OPEN multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:250 Previous definition here .././wxOil/xrc/EN/camelot.xrc:70 Warning wxID_CLOSE multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:214 Previous definition here .././wxOil/xrc/EN/camelot.xrc:74 Warning wxID_SAVE multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:280 Previous definition here .././wxOil/xrc/EN/camelot.xrc:78 Warning wxID_SAVEAS multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:286 Previous definition here .././wxOil/xrc/EN/camelot.xrc:83 Warning wxID_PRINT multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:262 Previous definition here .././wxOil/xrc/EN/camelot.xrc:87 Warning wxID_PREVIEW multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:268 Previous definition here .././wxOil/xrc/EN/camelot.xrc:91 Warning wxID_PRINT_SETUP multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:274 Previous definition here .././wxOil/xrc/EN/camelot.xrc:96 Warning ID_FILE_MRU_FILE1 multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:220 Previous definition here .././wxOil/xrc/EN/camelot.xrc:101 Warning wxID_EXIT multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:124 Previous definition here .././wxOil/xrc/EN/camelot.xrc:108 Warning wxID_UNDO multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:208 Previous definition here .././wxOil/xrc/EN/camelot.xrc:113 Warning wxID_CUT multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:154 Previous definition here .././wxOil/xrc/EN/camelot.xrc:117 Warning wxID_COPY multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:148 Previous definition here .././wxOil/xrc/EN/camelot.xrc:121 Warning wxID_PASTE multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:166 Previous definition here .././wxOil/xrc/EN/camelot.xrc:125 Warning ID_EDIT_PASTE_LINK multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:172 Previous definition here .././wxOil/xrc/EN/camelot.xrc:130 Warning ID_OLE_INSERT_NEW multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:358 Previous definition here .././wxOil/xrc/EN/camelot.xrc:134 Warning ID_OLE_EDIT_LINKS multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:352 Previous definition here .././wxOil/xrc/EN/camelot.xrc:138 Warning ID_OLE_VERB_FIRST multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:364 Previous definition here .././wxOil/xrc/EN/camelot.xrc:145 Warning ID_VIEW_TOOLBAR multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:382 Previous definition here .././wxOil/xrc/EN/camelot.xrc:149 Warning ID_VIEW_STATUS_BAR multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:376 Previous definition here .././wxOil/xrc/EN/camelot.xrc:156 Warning ID_WINDOW_NEW multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:400 Previous definition here .././wxOil/xrc/EN/camelot.xrc:160 Warning ID_WINDOW_CASCADE multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:394 Previous definition here .././wxOil/xrc/EN/camelot.xrc:164 Warning ID_WINDOW_TILE_HORZ multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:412 Previous definition here .././wxOil/xrc/EN/camelot.xrc:168 Warning ID_WINDOW_ARRANGE multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:388 Previous definition here .././wxOil/xrc/EN/camelot.xrc:175 Warning ID_HELP_INDEX multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:298 Previous definition here .././wxOil/xrc/EN/camelot.xrc:179 Warning ID_HELP_USING multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:304 Previous definition here .././wxOil/xrc/EN/camelot.xrc:184 Warning wxID_ABOUT multiply defined (global) .././wxOil/xrc/EN/camelot-strings.xrc:118 Previous definition here .././wxOil/xrc/EN/richard3-strings.xrc:10 Warning IDC_LIBPATH_HELP_BUTTON multiply defined (global) .././wxOil/xrc/EN/richard.xrc:59 Previous definition here Could not read dialogs for translation: No such file or directory at .././Scripts/build-resources.pl line 340. Makefile:296: *** "Resource build failed". Stop. make[1]: *** [camtypes.h.gch] Error 2 make: *** [all-recursive] Error 1 !!! ERROR: media-gfx/XaraLX-0.5.1203 failed. Call stack: ebuild.sh, line 1531: Called dyn_compile ebuild.sh, line 931: Called src_compile XaraLX-0.5.1203.ebuild, line 53: Called die
(In reply to comment #45) > Apart from these trivial matters, there's the more important matter of the GPL. > Basically, distributing part of XaraLX as GPL and part as wxWindows-3.1 and yet > another part (CDraw) under yet another license is simply not permitted under > the GPL. I'm sorry, but I don't understand your interpretation of the GPL. The GPL only applies to files that are licensed under the GPL. It's perfectly legal for Xara to license some of the files under a different license to the GPL, which is what they have done here. Xara are doing nothing wrong here that I can see. The only way they would be doing something wrong would be if they were relicensing files originally released under the GPL. Best regards, Stu
(In reply to comment #47) > I'm sorry, but I don't understand your interpretation of the GPL. The GPL only > applies to files that are licensed under the GPL. It's perfectly legal for > Xara to license some of the files under a different license to the GPL, which > is what they have done here. From section 2 of the GPL, 2nd version: These requirements apply to the modified work [XaraLX] as a whole. If identifiable sections of that work [CDraw] are not derived from the Program [XaraLX], and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them *as separate works*. But when you distribute the same sections [CDraw] as part of a whole which is a work based on the Program [XaraLX], the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole [XaraLX and CDraw], and thus to each and every part regardless of who wrote it. [comments between brackets and emphasis are mine] > Xara are doing nothing wrong here that I can see. The only way they would be > doing something wrong would be if they were relicensing files originally > released under the GPL. Of course Xara is doing nothing wrong: they are free to license XaraLX in whatever way seems fitting to them. However, you cannot redistribute XaraLX under the GPL according to section 2.b, taking into account the way in which the part (CDraw) and the whole (XaraLX) are licensed: "[2.] b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License." It is therefore impossible to (re)distribute or (re)publish XaraLX under the GPL (for anyone but the copyright holder). Either CDraw needs to be published separately or XaraLX cannot be claimed to be licensed under the GPL. To reestablish this as a trivial technical issue instead of continuing a prolonged judicial discussion: We would need a cdraw-bin package released under the CDraw license that a hypothetical xara{lx} ebuild would DEPEND upon. Kind regards, JeR
*** Bug 139622 has been marked as a duplicate of this bug. ***
"ebuild XaraLX-0.4.967.ebuild digest" returns: ---- /usr/overlay/media-gfx/XaraLX/XaraLX-0.4.967.ebuild: line 82: unexpected EOF while looking for matching `"' /usr/overlay/media-gfx/XaraLX/XaraLX-0.4.967.ebuild: line 84: syntax error: unexpected end of file !!! ERROR: media-gfx/XaraLX-0.4.967 failed. Call stack: ebuild.sh, line 1447: Called die !!! error sourcing ebuild !!! If you need support, post the topmost build error, and the call stack if relevant. [31;01m aux_get():[39;49;00m (0) Error in media-gfx/XaraLX-0.4.967 ebuild. (1) Check for syntax error or corruption in the ebuild. (--debug) ----------------------- emerge --info (for good measure) Gentoo Base System version 1.6.14 Portage 2.1-r1 (default-linux/x86/2005.1, gcc-3.4.5, glibc-2.3.6-r3, 2.6.15-gentoo-r1 i686) ================================================================= System uname: 2.6.15-gentoo-r1 i686 Celeron (Mendocino) dev-lang/python: 2.3.5, 2.4.2 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/gcc-config: 1.3.13-r2 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=i686" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/terminfo" CXXFLAGS="-O2 -march=i686" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LANG="en_GB.UTF-8" 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'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/proaudio /usr/overlay" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X alsa apache2 apm arts avi berkdb bitmap-fonts cjk cli crypt cups dga dlloader dri dssi dts dvd dvdread eds emboss encode foomaticdb fortran gcj gd gdbm gif gnome gpm gstreamer gtk gtk2 i8x0 imlib immqt-bc ipv6 isdnlog java jpeg jpg kde libg++ libwww live mad matroska mikmod mmx motif mp3 mpeg mysql ncurses nls offensive ogg oggvorbis opengl openssl oss pam pcre pdflib perl png pppd python qt qt3 qt4 quicktime readline real reflection sdl session spell spl ssl tcpd theora truetype truetype-fonts type1-fonts unicode vorbis win32codecs xanim xml2 xmms xorg xv zlib elibc_glibc input_devices_keyboard input_devices_mouse input_devices_evdev kernel_linux userland_GNU video_cards_i810" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS, PORTAGE_RSYNC_EXTRA_OPTS
Created attachment 91186 [details] xaralx-0.5-r1416.ebuild
I have made an ebuild for xaralx 0.6 revision 1479. Everything is available at http://www.gentoo-sunrise.org/svn/sunrise/media-gfx/xaralx/
Created attachment 94122 [details] xaralx-0.7-r1695.ebuild
version bump available: http://www.gentoo-sunrise.org/svn/reviewed/media-gfx/xaralx/xaralx-0.7_p1692.ebuild The installation part is completed now and it also installs some examples Have fun
*** Bug 144293 has been marked as a duplicate of this bug. ***
Created attachment 94687 [details] xaralx-0.7_p1692.ebuild Modyfied ebuild from gentoo-sunrise.org (MY_P && SRC_URI).
Created attachment 94690 [details] xaralx-0.7_p1709.ebuild Version bump.
*** Bug 145620 has been marked as a duplicate of this bug. ***
Updated in Sunrise to 0.7_p1744. Jiri: Once an ebuild is maintained Sunrise you shouldn't attach any further updates here in bugzilla -- you should make the update in Sunrise and then leave a note here about the update. Thanks.
After encountering problems updating the Xara ebuilds in Sunrise I've discovered we shouldn't bump to a newer version unless the version is marked "recommended" by upstream. For all versions not marked "recommended", upstream removes the packages from the download servers after approximately 8 days [1], so there's no point in making ebuilds for them. Only the "recommended" versions are considered stable release builds; all others are treated as maintenance builds. [1] http://www.xaraxtreme.org/maillists/archive/dev/msg00020.html
*** Bug 152586 has been marked as a duplicate of this bug. ***
Created attachment 100311 [details] Xara LX 0.7r1763
(In reply to comment #62) > Created an attachment (id=100311) [edit] > Xara LX 0.7r1763 As explained in comment #60, unstable nightly builds of Xara such as 0.7 rev 1763 do not belong in Portage. Only release versions such as 0.7 rev 1692 are suitable, so don't bother making ebuilds for the nightlies. (From my experiences trying to use the nightly revisions for real work, I can tell you they're too buggy to use anyhow.) Also, Xara ebuilds are now being maintained in the Sunrise overlay [1], so please work on them there [2] -- don't attach any further ebuilds to this Bugzilla entry. [1] http://www.gentoo-sunrise.org/sunrise/browser/reviewed/media-gfx/xaralx [2] http://www.gentoo-sunrise.org/sunrise
*** Bug 156285 has been marked as a duplicate of this bug. ***
Just an observation that I don't think it significant enough to warrant posting a seperate bug for, They are no longer calling it "Xara LX" http://www.xaraxtreme.org/ quote<<EOF Xara Xtreme for Linux is a powerful, general purpose graphics program for Unix platforms including Linux, FreeBSD and (in development) OS-X. Formely known as Xara LX, it is based on Xara Xtreme for Windows, which is the fastest graphics program available, period. The Xara Xtreme source code was made available open-source in early 2006, and is being ported to Linux. This process is almost complete and Xara Xtreme for Linux is available for download now. EOF
*** Bug 171153 has been marked as a duplicate of this bug. ***
Created attachment 116466 [details] xaralx-0.7_p1766.ebuild XaraLx ebuild for the latest version.
(In reply to comment #67) > Created an attachment (id=116466) [edit] > The latest xaralx > > XaraLx ebuild for the latest version. Hi Ivan. Please see comment #63 for why you shouldn't post any new ebuilds here. The previous Xara release ebuild is in the Sunrise overlay [1]. You should have based your ebuild on that, because there's so many problems with your current ebuild that it's not worth correcting here. If you'd like help improving it, please visit #gentoo-sunrise on Freenode. There you can also get access to commit it to the overlay. Please also note from comment #65 that the name has been changed from Xara LX to Xara Xtreme (even though the distribution package is still named "xaralx", presumably for backwards packaging compatibility). [1] http://overlays.gentoo.org/proj/sunrise/browser/reviewed/media-gfx/xaralx
Oh, and also see comment #60 about which Xara builds are release builds. Rev. 1766 is *not* a release build, it's the equivalent of a nightly build. Hence it doesn't belong in the tree.
*** Bug 176944 has been marked as a duplicate of this bug. ***
*** Bug 203047 has been marked as a duplicate of this bug. ***
Why Xara is not in official portage? Lack of maintainers?
long time in overlay, can't this be added to official portage?
reopening for sunrise policy (ebuilds in sunrise need an open bug assigned to maintainer-wanted).
0.7r1785 seems to be current... Found at softpedia: http://mac.softpedia.com/get/Graphics/Xara-Xtreme.shtml Download link is: http://downloads2.xara.com/opensource/XaraLX-0.7r1785.tar.gz I hear that Xara LX has been renamed to Xara Xtreme, but I'm not sure if this is also true for this specific release.
Created attachment 234193 [details] xaralx-0.7_p1785.ebuild
Created attachment 234195 [details, diff] xaralx-wxOil-0.7_p1785.patch
(In reply to comment #77) > Created an attachment (id=234195) [details] > xaralx-wxOil-0.7_p1785.patch > Unfortunately, the ebuild+patch don't work for me: MAKEOPTS="-j1" basebar2.cpp: In constructor ‘BaseBar::BaseBar()’: basebar2.cpp:364: note: #pragma message: basebar2.cpp(364) : Port Message: Not using dither pattern basebar2.cpp: In member function ‘virtual void BaseBar::SetFormatVariables()’: basebar2.cpp:499: note: #pragma message: basebar2.cpp(499) : Port Message: BaseBar::SetFormatVariables - do nothing basebar2.cpp: In member function ‘void BaseBar::CloseCombos()’: basebar2.cpp:527: note: #pragma message: basebar2.cpp(527) : Port Message: BaseBar::CloseCombos - do nothing basebar2.cpp: In member function ‘virtual wxRect BaseBar::GetFormatRect(DockBarType)’: basebar2.cpp:702: note: #pragma message: basebar2.cpp(702) : Port Message: BaseBar::GetFormatRect - do nothing basebar2.cpp: In member function ‘virtual DockBarType BaseBar::IsPointerOverDock(wxPoint)’: basebar2.cpp:776: note: #pragma message: basebar2.cpp(776) : Port Message: BaseBar::IsPointerOverDock - do nothing basebar2.cpp: In member function ‘virtual wxRect BaseBar::SetBarSize(DockBarType, BOOL)’: basebar2.cpp:825: note: #pragma message: basebar2.cpp(825) : Port Message: BaseBar::SetBarSize - do nothing basebar2.cpp: In member function ‘BOOL BaseBar::Show(DialogBarOp*)’: basebar2.cpp:923: note: #pragma message: basebar2.cpp(923) : Port Message: BaseBar::Show - do nothing basebar2.cpp: In member function ‘BOOL BaseBar::Hide(DialogBarOp*)’: basebar2.cpp:1003: note: #pragma message: basebar2.cpp(1003) : Port Message: BaseBar::Hide - do nothing basebar2.cpp: In member function ‘BOOL BaseBar::Create(DialogBarOp*)’: basebar2.cpp:1041: note: #pragma message: basebar2.cpp(1041) : Port Message: BaseBar::Create - do nothing basebar2.cpp: In member function ‘BOOL BaseBar::RecreateAt(KernelBarPos, DockBarType, BaseBar*, DialogBarOp*, wxWindow*)’: basebar2.cpp:1226: note: #pragma message: basebar2.cpp(1226) : Port Message: BaseBar::RecreateAt - do nothing basebar2.cpp: In member function ‘BOOL BaseBar::Recreate(DockBarType, BaseBar*, DialogBarOp*, BOOL)’: basebar2.cpp:1346: note: #pragma message: basebar2.cpp(1346) : Port Message: BaseBar::Recreate - do nothing basebar2.cpp: In member function ‘KernelBarPos* BaseBar::GetBarPosition()’: basebar2.cpp:1671: note: #pragma message: basebar2.cpp(1671) : Port Message: BaseBar::GetBarPosition - do nothing basebar2.cpp: In member function ‘BOOL BaseBar::FormatLineFeeds(INT32, wxSize*, INT32*)’: basebar2.cpp:2032: note: #pragma message: basebar2.cpp(2032) : Port Message: BaseBar::FormatLineFeeds - do nothing basebar2.cpp: In member function ‘UINT32 BaseBar::GetNearestControl(wxPoint)’: basebar2.cpp:2249: note: #pragma message: basebar2.cpp(2249) : Port Message: BaseBar::GetNearestControl - do nothing basebar2.cpp: In member function ‘virtual BOOL BaseBar::FormatFloatingBar(BOOL, ForceControlSize)’: basebar2.cpp:2464: note: #pragma message: basebar2.cpp(2464) : Port Message: BaseBar::FormatFloatingBar - do nothing basebar2.cpp: In member function ‘virtual BOOL BaseBar::FormatHorizontalBar(BOOL, ForceControlSize)’: basebar2.cpp:2772: note: #pragma message: basebar2.cpp(2772) : Port Message: BaseBar::FormatHorizontalBar - do nothing basebar2.cpp: In member function ‘virtual BOOL BaseBar::FormatVerticalBar(BOOL, ForceControlSize)’: basebar2.cpp:3021: note: #pragma message: basebar2.cpp(3021) : Port Message: BaseBar::FormatVerticalBar - do nothing basebar2.cpp: In member function ‘void* BaseBar::GetModuleInst(const BarControlInfo*, UINT32*)’: basebar2.cpp:3257: note: #pragma message: basebar2.cpp(3257) : Port Message: BaseBar::GetModuleInst - do nothing basebar2.cpp: In member function ‘BOOL BaseBar::CreateControlItem(DLGITEMTEMPLATE*, BarControl*, void*, UINT32)’: basebar2.cpp:3614: note: #pragma message: basebar2.cpp(3614) : Port Message: BaseBar::GetModuleInst - do nothing basebar2.cpp: In member function ‘void BaseBar::InformControlsDead()’: basebar2.cpp:4313: note: #pragma message: basebar2.cpp(4313) : Port Message: BaseBar::InformControlsDead - do nothing basebar2.cpp: In member function ‘virtual void BaseBar::StartDrag(wxPoint, DlgDragType)’: basebar2.cpp:4465: note: #pragma message: basebar2.cpp(4465) : Port Message: BaseBar::StartDrag - do nothing basebar2.cpp: At global scope: basebar2.cpp:4568: error: ‘#pragma’ is not allowed here basebar2.cpp:4597: error: expected ‘}’ before ‘wxEventTableEntry’ basebar2.cpp:4597: error: expected ‘,’ or ‘;’ before ‘wxEventTableEntry’ basebar2.cpp:4597: error: expected declaration before ‘}’ token make[2]: *** [libwxOil_a-basebar2.o] Error 1 make[2]: Leaving directory `/var/tmp/portage/media-gfx/xaralx-0.7_p1785/work/XaraLX-0.7r1785/wxOil' make[1]: *** [all] Error 2 make[1]: Leaving directory `/var/tmp/portage/media-gfx/xaralx-0.7_p1785/work/XaraLX-0.7r1785/wxOil' make: *** [all-recursive] Error 1 * ERROR: media-gfx/xaralx-0.7_p1785 failed: * emake failed * * Call stack: * ebuild.sh, line 48: Called src_compile * environment, line 2380: Called _eapi0_src_compile * ebuild.sh, line 606: Called _eapi2_src_compile * ebuild.sh, line 640: Called die * The specific snippet of code: * emake || die "emake failed" * * If you need support, post the output of 'emerge --info =media-gfx/xaralx-0.7_p1785', * the complete build log and the output of 'emerge -pqv =media-gfx/xaralx-0.7_p1785'. * This ebuild is from an overlay named 'ownage': '/usr/local/portage/ownage/' * The complete build log is located at '/var/tmp/portage/media-gfx/xaralx-0.7_p1785/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/media-gfx/xaralx-0.7_p1785/temp/environment'. * S: '/var/tmp/portage/media-gfx/xaralx-0.7_p1785/work/XaraLX-0.7r1785' >>> Failed to emerge media-gfx/xaralx-0.7_p1785, Log file: >>> '/var/tmp/portage/media-gfx/xaralx-0.7_p1785/temp/build.log' * Messages for package media-gfx/xaralx-0.7_p1785: * ERROR: media-gfx/xaralx-0.7_p1785 failed: * emake failed * * Call stack: * ebuild.sh, line 48: Called src_compile * environment, line 2380: Called _eapi0_src_compile * ebuild.sh, line 606: Called _eapi2_src_compile * ebuild.sh, line 640: Called die * The specific snippet of code: * emake || die "emake failed" emerge --info snippet: # emerge --info Portage 2.2_rc67 (default/linux/amd64/10.0/desktop/kde, gcc-4.4.4, glibc-2.11.2-r0, 2.6.34 x86_64) ================================================================= System uname: Linux-2.6.34-x86_64-Intel-R-_Core-TM-2_Duo_CPU_L9400_@_1.86GHz-with-gentoo-2.0.1 Timestamp of tree: Tue, 22 Jun 2010 19:15:02 +0000 app-shells/bash: 4.1_p7 dev-java/java-config: 2.1.11 dev-lang/python: 2.6.5-r2, 3.1.2-r3 dev-util/cmake: 2.8.1-r2 sys-apps/baselayout: 2.0.1 sys-apps/openrc: 0.6.1-r1 sys-apps/sandbox: 2.2 sys-devel/autoconf: 2.65-r1 sys-devel/automake: 1.9.6-r3, 1.10.3, 1.11.1 sys-devel/binutils: 2.20.1-r1 sys-devel/gcc: 4.4.4-r1 sys-devel/gcc-config: 1.4.1 sys-devel/libtool: 2.2.10 virtual/os-headers: 2.6.34 ABI="amd64" ACCEPT_KEYWORDS="amd64 ~amd64"
Created attachment 243171 [details] ebuild for xaralx with libpng-1.4.3
Created attachment 243173 [details, diff] patch for xaralx-0.7_p1785
*** Bug 358991 has been marked as a duplicate of this bug. ***
Created attachment 291917 [details, diff] xaralx-0.7_p1785-libpng15-incomplete.patch xaralx-0.7_p1785 fails to build with libpng-1.5. This happens because it tries to access private struct members, which has been deprecated and is not available anymore. I did a little bit of hacking and found 2 files that need patching: wxOil/pngutil.cpp and wxOil/outptpng.cpp The first one is quite easy, and the attached patch fixes it. The second one requires a lot more effort, as there are dozens of lines that need to be updated. There might be another files needing patches, but these two are a good starting point.
Created attachment 315375 [details, diff] xaralx-0.7_p1785-libpng15.patch I have make this patch which fixes compilation with new libpng. Updated ebuild is already in the Sabayon overlay. Enjoy!
Hello, everyone. It seems that at least one ebuild related to this bug exists in the Sunrise overlay at the moment. However, I have to regretfully announce that after a long inactivity period the Sunrise project has been discontinued and the related overlay will be eventually removed. For this reason, I'd like to ask you to reevaluate the ebuilds and consider moving them. If you'd like to maintain a package from Sunrise in Gentoo, please take a look at our Proxy Maintainers [1] project. Please make sure to take ebuilds from the unreviewed developer Sunrise repository [2] rather than the -reviewed one, since the latter has not been updated for over a year. While at it, please note that: 1. Adding a package to Gentoo requires declaring yourself as an active maintainer for it. All bugs regarding the package will be assigned to you, and you will be expected to maintain it. 2. Some packages may not be suitable for addition anymore. While there's no strong rules that would prevent you from adding a package, it may be a bad idea to add old-unmaintained packages that will shortly result in a large number of bugs reported with no solution. If that is the case, please close the bug as RESOLVED/OBSOLETE to make it easier to find packages worth adding. 3. Some of the bugs were already closed as WONTFIX/OBSOLETE/... while the relevant ebuild was kept in Sunrise. If you disagree with the original decision, you still can add the ebuild via proxy-maint. 4. Pleaes note that many of the Sunrise ebuilds are old and may be buggy. If you decide to move them, please make sure to update/clean them up. The proxy-maint team will also review your ebuilds, therefore making sure they land in Gentoo in good quality. Once again, thank you for your contribution. We hope that you will still want to contribute to Gentoo, through proxy-maint or otherwise. [1]:https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers [2]:https://gitweb.gentoo.org/proj/sunrise.git/
