Changing the way Clojure is *packaged* to meet the needs of an alien build system is the tail wagging the dog.
Clojure uses the de facto Java standard (Maven) to deal with these things. Clojure's build depends on a number of plugins (maven-release-plugin, maven-source-plugin, maven-jar-plugin, maven-assembly-plugin, build-helper-maven-plugin, maven-antrun-plugin, and maven-compiler-plugin), and most of these dependencies have been present for several releases already, so this is not a new problem. Whatever technique prevents those items from being downloaded from the Internet should also be considered for test.generative. Stu On Sun, Dec 23, 2012 at 4:11 PM, Jochen Schmitt <joc...@herr-schmitt.de>wrote: > On Sun, Dec 23, 2012 at 12:45:50PM -0800, Andy Fingerhut wrote: > > > Are there no other RPMs that require Internet access to complete their > build? > > > > e.g. no others that use Maven to pull in dependencies before building? > > Dependencies should be solved by the specification of BuildRequires > statements > in the SPEC file, so the build system will install the packages which are > required > to build a package before the build will be start. > > > If there is no provision for that, I'd open up the question to others > with more experience in these matters: How would you recommend that someone > create an RPM for Clojure on a build machine with no Internet access? > > Sorry, I'm talking about the official build system of the Fedora projejct > and > the download of data during the build process may a violatation of the > packaging policies. > > > The only way I can think of would be to pull in the dependencies on a > machine with Internet access, and make a package available to the RPM build > machine with all dependencies included. > > ??? > > > Either that, or get a pre-built JAR file for Clojure from the official > distribution locations (e.g. the Maven repo) and put that into an RPM. > > Using of pre-built JAR files in a package is also a violation of the > packaging > policy which state that all stuff should be built from soruce. > > Because it's looks like, thest test.gnerative may be a speicial JAR file > for Clojure, the best way may to include it into the official Clojure > soruce pacakge. > > In the meanwhile, I have found a way to suppres the test step in the > ant script. > > Best Regards: > > Jochen Schmitt > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with > your first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
