1:49 p.m.
Are we planning to have a way to host source tarballs and/or rpms? I'm
not sure of specific license requirements, but the vast majority of
projects seem to provide at least source tarballs. At the least, it
lets people get a specific version of the project(s) without digging
through git tags.
Mike
5:10 p.m.
--0rSojgWGcpz+ezC3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Oct 28, 2011 at 02:49:08PM -0400, Mike Burns wrote:
Are we planning to have a way to host source tarballs and/or rpms?
I'm
not sure of specific license requirements, but the vast majority of
projects seem to provide at least source tarballs. At the least, it
lets people get a specific version of the project(s) without digging
through git tags.
It's a MUST requirement for an open source project, really - gzip or
bzip tarballs, zip if appropriate of at least each release, going back
in time. Packages ideally end-up in the respective distros, until then
we SHOULD host them via ovirt.org. (I reckon JARs & WARs may be
already compressed, if we're providing those we can probaly leave them
as .jar/.war files?)
Now the how of it is the trick. We can start doing it manually, create
a directory structur off ovirt.org that makes sense, etc. But don't we
really want these generated as part of the release build process?
Then don't we want those builds + checksums pushed automagically to
the above ovit.org directory? Then might we want to provide nightly
builds in some way?
So no rush on picking the how, except that the directory structure we
build first would ideally match the future structure. And probably
some other stuff.
- Karsten
--=20
name: Karsten 'quaid' Wade, Sr. Community Gardener
team: Red Hat Community Architecture & Leadership
uri: http://communityleadershipteam.org
http://TheOpenSourceWay.org
gpg: AD0E0C41
--0rSojgWGcpz+ezC3
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iD8DBQFOqyho2ZIOBq0ODEERAgT3AKCr+dsOzJHoDvBdXlTuhV91FGeGeQCgqngq
dofEI6oCk2lTwhPKBT3+pbo=
=R8t4
-----END PGP SIGNATURE-----
--0rSojgWGcpz+ezC3--
5:40 p.m.
-----Original Message-----
From: infra-bounces(a)ovirt.org [mailto:infra-bounces@ovirt.org] On Behalf
Of Karsten
Wade
Sent: Saturday, October 29, 2011 0:11 AM
To: infra(a)ovirt.org
Subject: Re: Hosting of source tarballs and rpms
On Fri, Oct 28, 2011 at 02:49:08PM -0400, Mike Burns wrote:
> Are we planning to have a way to host source tarballs and/or rpms?
I'm
> not sure of specific license requirements, but the vast majority
of
> projects seem to provide at least source tarballs. At the least, it
> lets people get a specific version of the project(s) without digging
> through git tags.
It's a MUST requirement for an open source project, really - gzip or
bzip tarballs, zip if appropriate of at least each release, going back
in time. Packages ideally end-up in the respective distros, until then
we SHOULD host them via ovirt.org. (I reckon JARs & WARs may be
already compressed, if we're providing those we can probaly leave them
as .jar/.war files?)
Now the how of it is the trick. We can start doing it manually, create
a directory structur off ovirt.org that makes sense, etc. But don't we
really want these generated as part of the release build process?
Then don't we want those builds + checksums pushed automagically to
the above ovit.org directory? Then might we want to provide nightly
builds in some way?
So no rush on picking the how, except that the directory structure we
build first would ideally match the future structure. And probably
some other stuff.
We do need to place the ovirt-jboss-5-as rpm somewhere to make it easy for
both devel and users.
Then we'll want to publish the rpms for the different components (to make
it easy for users to deploy).
So just tell us where to put it for now, until we resolve the long term
question I guess
4970
days inactive
4970
days old
2 comments
3 participants
participants (3)
-
Itamar Heim -
Karsten Wade -
Mike Burns