[Users] Proposal packaging Zimlets/Extensions via OS repos using RPM/DEB

Barry De Graaff barrydg at zetalliance.org
Mon Apr 18 22:39:18 CEST 2016


Long story short, I guess building the repo first and then see where to host it, is the way to go!


> IMO, the fact that the Alliance does not have a legal status at this point is causing the issue here. Synacor has demonstrated by actions that they are opening up the processes and project around Zimbra/ZCS. I think right now, it's > the legal things that are getting in the way. Legal issues that are required by the nature of Synacor being listed and monitored by regulatory agencies in the US.

So far I have yet to see any public announcement of Zimbra Inc. on the alliance, so stating it is the Alliance' legal status, that is causing the issue... is a bit short.




----- Original Message -----
From: "Sommerseth, David" <dazo at eurephia.org>
To: "Quanah Gibson-Mount" <quanah at zimbra.com>
Cc: "Barry De Graaff" <barrydg at zetalliance.org>, users at lists.zetalliance.org, devel at lists.zetalliance.org
Sent: Monday, April 18, 2016 9:43:11 PM
Subject: Re: Proposal packaging Zimlets/Extensions via OS repos using RPM/DEB

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 18/04/16 21:31, Quanah Gibson-Mount wrote:
>> For building the RPMs ... I don't know what kind of technologies have
>> been considered or chosen.  But I highly recommend to look into mock
>> [1], which gives you great control of the end result.  Fedora, Fedora
>> EPEL and RHEL is built using mock under the hood.  And the big plus is,
>> if you have a working rpmbuild routine moving to mock is a no brainer.
> 
> Hi David,
> 
> I've no objection to using Mock as long as it is present in RHEL6.

It is.  I have used mock on SL6 and RHEL6 to build a few internal YUM/RPM
repositories.  Mock ensures that all builds are done in clean buildroots
with a predictable set of packages, hence you don't get into dependency
surprises very easily.

IIRC, enable Fedora EPEL and do 'yum install mock' .... then have a look at
the profiles in /etc/mock .... and kick off a build like this:

    mock -r $PROFILE --rebuild /path/to/src.rpm

Then sit back and wait for the brewed RPM to be served in /var/lib/mock


David S.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEARECAAYFAlcVOM8ACgkQDC186MBRfro1hACdEEQlBJ5RU6EQSmcRemaFA6mD
I6QAn1IU4neU6tcCnwqvMUR/6hwUGqYy
=7XDY
-----END PGP SIGNATURE-----




More information about the Users mailing list