Looks like very promising.

Thanks Adam !

Jacques

De : "Adam Heath" <[EMAIL PROTECTED]>
> Vince M. Clark wrote:
> > +1 for packaging! Ultimately it is important to support as many platforms 
> > as possible, but Debian is a great start.
> >
> > What OfBiz "version" do you base your packages on? Also, do you assume a 
> > particular database, or require one as a package
dependency? Does your packaging provide any "smart" setup such as prompting for 
database username/pw?
>
> I've done several upgrades to it.  Started last February.  I'm currently
>  mostly tracking against HEAD.  I could produce ones against a release
> target if need be.
>
> No, I don't assume any particular database.  The package I built
> suggests mysql or postgres(but doesn't depend).  Then, during
> installation, I use debconf, combined with dbconfig-common, to configure
> the database.  I query which are installed, then ask which you want to
> use.  In addition to the two above, I also support configuring derby,
> which runs embedded inside ofbiz.
>
> dbconfig-common takes care of prompting for database values; namely,
> host/port/dbname/username/password.  I then take that info, and use it
> to drive an xslt that modifies entityengine.xml.
>
> I've moved all config/, data/, ofbiz-component.xml, servicedef/,
> component-load.xml, controller.xml, web.xml, *.css, ftl templates into
> /etc/ofbiz, and they get treated as dpkg conffiles.
>
> Runtime data is moved into /var/lib/ofbiz, and log data into /var/log/ofbiz.
>
> However, as far as the java runtime is concerned, everything looks
> normal; I make symlinks to the above from /usr/share/ofbiz.
>
> I compile all java code, but do *not* ship it as part of the package.  I
> only ship the jars in build/lib.
>
> I have one main ofbiz package, then an ofbiz-specialpurpose.  I should
> probably split out ofbiz-applications, but haven't done so yet.  I don't
> want to micro-package, as it makes it more difficult to understand.
>
> The last version I uploaded to our local repository is based on 582338.
>

Reply via email to