Traditionally in the unix world, optional software goes in /opt. So, I have the following:
/opt/ofbiz.1104/ /opt/ofbiz.1004/ Etc. It is up to you. Also, regarding your comparison to autoconf, etc, in the java world, it is "ant", which looks for "build.xml" files. In the ofbiz world, there are a lot of build.xml files, including a master one at the top, which is called when compiling ofbiz. On Tue, Jul 31, 2012 at 2:15 PM, Ted Byers <[email protected]> wrote: > > -----Original Message----- > > From: Adrian Crum [mailto:[email protected]] > > Sent: July-31-12 4:46 PM > > To: [email protected] > > Subject: Re: Install location of OFBiz: still getting started ... > > > > In this type of project, it doesn't work the same as a C++ library or > similar. We > > have no idea what platform you plan to deploy on, and there are too many > > options to attempt a universal installation script. > > > > You can write a shell script to do an SVN checkout and build for the > target > > server (pull the project to the server or push the project to the > server). > The > > same script could be used to remove unwanted files. If you want to remove > the > > .svn folders from your deploy copy, you can use the SVN export command. > > > > -Adrian > > > Hi Adrian > > Thanks > > The same problem exists in the C++ world. There are many different > configurations of a variety of distributions of Linux, not to mention the > other variants of Unix and the versions of Windows. That is why, in the > C++ > world, they developed autoconf and automake, and a common file shipped with > most libraries and Unix programs is 'configure.sh', which when finished > makes various configuration files and, most importantly, the makefiles. > That is a script that you use to define where everything is and where > everything is to go. The fancier configure.sh scripts will actually > specify > which parts of the project to build depending on what resources are > available. For example, the project may be able to use a png library, if > it > is present, but will build fine, and either doesn't build support for > graphics files, or it will use another graphics file format if configure.sh > finds some other graphics file it knows how to use. So, even though the > project developers have no idea what your system is or how it is > configured, > they can make use of whatever you have installed that it makes sense for > them to use, as long as you pass the appropriate info as arguments to > 'configure.sh'. > > But that doesn't tell me where the ofbiz directory tree contents ought to > go. I can see a number of candidate directories that logically ought to > take at least some of the files; but if it is like some of the other > servers > I have installed, there will be some stuff put into (a subdirectory of) > /etc, and other stuff put into /srv, and maybe /opt. And some of the files > probably ought to go into /etc/init.d; but what ought to go where on a Suse > Linux box? Where have others who use Suse Linux put OFBiz? > > Thanks > > Ted > >
