new ebuild for scala (! not scala-bin)
Created attachment 96991 [details] scala-2.1.8.ebuild I've put RESTRICT="fetch" to rename the source tarball. I don't know if it is possible to do that otherwise.
Hello. If I am not mistaken on what you are trying to do, you can do something like this: inherit versionator MY_P="R_$(replace_all_version_separators '-')" SRC_URI="http://scalasvn.epfl.ch/cgi-bin/viewvc.cgi/scala/tags/${MY_P}.tar.gz" ... instead of RESTRICT="fetch", renaming the package and manually fetching it (which sounds like a bad idea). For more information, I encourage you to take a look at the Gentoo devmanual [1] if you haven't already. Kind regards, Aggelos
Forgot to mention the URI. [1] http://devmanual.gentoo.org/ebuild-writing/index.html
--MY_P="R_$(replace_all_version_$_separators '-')" I've done this with FILE="R_${PV//./_}". I didn't know versionator eclass. But I want to rename the file R_2_1_8.tar.gz because i think that isn't a good name. Scala sources are only available by svn and this tarball is autogenerated by viewvc (R_2_1_8 as the directory). I think that program name should figure in tarball, otherwise it can bring to name conflict. If you want I modify the ebuild to use subversion eclass, but I've found nicer to use the tarball. --Forgot to mention the URI Do you mean in pkg_nofetch()? I "autofetch" the file in it. The message isn't clear. I meant: "The file is now fetched. rerun emerge to build" or did you mean the incorrect SRC_URI? (only the filename is incorrect) Thanks, greetings Michel
sorry for twice post! my network/internet issue!
With "Forgot to mention the URI.", I meant that I forgot to provide the link to the Gentoo devmanual I wrote about in my initial comment. Since your ebuild downloads a tarball that is automatically generated, it is still considered to be a "live" ebuild AFAIK; thus I see no reason why you can't use the SVN eclass to make your life easier. Note, however, that such live ebuilds are generally discouraged. It would be better if you made an ebuild that downloaded and compiled a static tarball of a predefined version (if there is one). As for renaming the tarball, I still see no reason to do it (even if you think it's ugly ;-)). If I were you, I would keep its name as-is; this would be much more consistent and wouldn't introduce unexpected behavior. Again, I encourage you to take a look at the Gentoo devmanual (http://devmanual.gentoo.org/). It's pretty well-written and informative, and I guess it will answer many of your questions. Regards, Aggelos
Created attachment 97043 [details] scala-2.1.8.ebuild new ebuild. fetch restriction removed. source doc and examples flag added.
Created attachment 97044 [details, diff] scala-nodoc.patch: disable scaladoc generation
Created attachment 103031 [details] revised ebuild for scala-2.3.0 - new scala version - removed scala-nodoc.patch - detect if it is a minor or a patch scala distribution to adjust ant target
Created attachment 115092 [details] revised ebuild for scala 2.4.0 This is just an updated version of the 2.3.0 patch, to cope with some directory name changes. There's plenty of room for improvement in it, but it works.
*** Bug 126471 has been marked as a duplicate of this bug. ***
Today is your lucky day, for I'm taking care of this! I will add it, how soon depends on how many times I will have to recompile this monstrosity till it behaves like I want: BUILD SUCCESSFUL Total time: 21 minutes 35 seconds
In CVS, thanks everyone. AMD64: please add ~amd64 keyword so we have the same as scala-bin and can remove that after this get stable. Please test with FEATURES=test to see if tests are ok, and USE=doc to see if 512M is enough for this beast to build and generate docs also on amd64... Be patient as both take a LONG time.
Added to ~amd64. Thank you for everyones work. Closing.
*** Bug 98103 has been marked as a duplicate of this bug. ***
