>On 2/11/07, Lucas C. Villa Real ><[EMAIL PROTECTED]> wrote: >> On 2/4/07, Hi There <[EMAIL PROTECTED]> wrote: >> > Sent that last one off a little to soon. >> > >> > This seems to work OK (the last one wasn't getting >> > anything moved over to $target) >> > Lucas (or anyone) should take a look at the included >> > jre and see where it belongs and if/how it should be >> > symlinked in, there are conflicting files. >> >> Hi Mike, >> >> Since recipes are used for source code *only*, it's better to provide >> this as a script that can be downloaded from the site instead. On the
Hmm, well there are definitely some other recipes that aren't source code only. Rar and most of the fonts come to mind. My question is why not allow recipes to distribute binary-only software? Gobo's recipes are a perfect way to "distribute" proprietary software without running into problems with redistributing the executable. Most of them need to run makefiles, do the symlinking, etc. same as the source code versions, they just skip the actual compile step. Also, a script for downloading the software doesn't provide all of the management facilities used with packages and recipes. What if another recipe requires a version of JDK > 1.4? Or I need to check to make sure the right versions of glibc, ssl, and cups are installed before installing Acrobat Reader? Can't manage the dependencies with just a script. >> other hand, Java already made their source code free, in a project >> named Hotspot, which is available at >> https://openjdk.dev.java.net/hotspot/ for download. >> >> It might be better to just create a recipe for that. >I won't be able to put time on this, but I've just commited a feature >in Compile which allows one to specify svn username and password, so >that it becomes simple to have a working recipe for the subversion >snapshot of the HotSpot JDK. Here's its skeleton. >Feel free to enhance it: > ># Recipe (MakeRecipe) for HotSpot by Lucas C. Villa >Real, on Sun Feb >11 12:23:50 BRST 2007 ># Recipe for version svn by Lucas C. Villa Real, on Sun Feb 11 >12:23:50 BRST 2007 >compile_version=1.8.2-CVS >svn="https://[EMAIL PROTECTED]/svn/openjdk/hotspot/trunk" >svn_username=guest >svn_password= >dir=hotspot > >As far as I could see, one needs to call make from >inside the 'make' >dir, while also having to have a previous JDK >installed in order to >bootstrap the build. Putting JDK in >Resources/BuildDependencies file >might be enough for now, until we have a binary JDK generated by this >recipe. > >-- >Lucas >powered by /dev/dsp Nice, I like the svn feature! I don't think it's going to be helpful in getting a JRE/JDK onto someone's computer, though. The hotspot source code doesn't look like a full-featured jdk, with javadocs and examples. And needing a jdk installed before you can compile it doesn't make the recipe helpful for your average user (if they already have the jdk properly installed, why dl and compile 100+ MBs just to reinstall the jdk?) The hotspot source looks like it's more for hackers interested in tinkering w/ the jdk, not in actually using it. The current model for recipes works just fine for proprietary binary programs, and would be very useful for end users who want/need to install them, and there already are binary only recipes, so why not just allow them? If you still don't think it's the way to go, maybe a new recipe type that is just for distributing binaries should be created? I have recipes for Acrobate Reader, latest rar, and the jdk, I was going to wait on doing flash until I got some feedback on the jdk recipe (glad I waited :) -Mike ____________________________________________________________________________________ Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
