----- Original Message -----
From: "Jiri Belka" <jbelka(a)redhat.com>
To: "Alon Bar-Lev" <alonbl(a)redhat.com>
Cc: users(a)ovirt.org
Sent: Tuesday, January 8, 2013 11:14:49 AM
Subject: Re: [Users] OS-independent ovirt-engine distribution archive
On Tue, 8 Jan 2013 04:03:58 -0500 (EST)
Alon Bar-Lev <alonbl(a)redhat.com> wrote:
> So I guess you can download rpms from the internet and not maven
> artifacts...
That's what I'm doing right now...
>
> Building using maven will prepare a full distribution exactly as
> you
> need, you just need to build it in a computer that is connected to
> the internet and then wrap up the resources and transfer it into
> the
> internal network.
This is what I would like but it should be done by ovirt team itself.
BSD port systems (are generally just Makefiles) can _only_ download
official archives and build them "locally".
When using maven the whole concept of "official" archive is different.
BSD ports build from source, so it should download sources, and sources do not include any
of the external dependency nor binaries.
Am I right so far?
The problem with maven is that it downloads dependencies during source build, which is
invalid approach as far as build methodology is concerned... but it is what it is.
The Fedora project added wrapper to force maven to use local repository and for maven
artifacts to be installed at this local repository. This is healthy solution as you build
dependencies as standard packages, then maven will fetch and use these local packages.
What you seek is binary distribution so ports will use binaries, is that matches *BSD
policy?
> Of course help will be appreciate, we are planning to solve the
> setup
> issue by rewriting it to match otopi infrastructure it will be one
> step closer to be able to customize it to different distributions.
That would be nice.
jbelka