RE: RPMS or RPM Spec file for cfengine?

[Villalovos, John L]

Personally I think it would be great if there was a SPEC file included
in the tarball.  So if this SPEC file gets added that would be a good
thing.

And actual RPMS and SRPMS would be a nice bonus for the lazy types but
not needed.

Thanks
John

John Villalovos
Intel Corporation 
15400 NW GREENBRIER PKWY # CO5-162
BEAVERTON, OR  97006-5723
(503) 677-5777   Fax: (503) 677-6670

GPG 1.+/PGP 5.+/ DSS/Diffie Helman
http://www.sodarock.com/JohnVillalovos-gpgkey.txt
1024D/1A25D86C 2F24 AD89 E5D5 C92B 7FE2  F878 7ED5 2D38 1A25 D86C

My opinions are my own and NEVER the opinions of Intel Corporation.  I
am but a tiny, insignificant, infinitesimal (1/80000) cog in the giant
machine of Intel :)  

> -----Original Message-----
> From: Juha Ylitalo [mailto:juha.o.ylitalo@nokia.com] 
> Sent: Monday, April 21, 2003 11:14 PM
> To: ext mark@iu.hio.no
> Cc: Villalovos, John L; help-cfengine@gnu.org
> Subject: Re: RPMS or RPM Spec file for cfengine?
> 
> 
> On Fri, 2003-04-18 at 21:37, ext mark@iu.hio.no wrote:
> ...
> > I would be happy to make rpms and debs if someone gave me a simple
> > way of doing it. Perhaps someone else could maintain it on the 
> > Savannah site. I don't use these myself,  being somewhat closer
> > to cfengine :).
> 
> Having separate project for single spec file (in RPMS case) 
> sounds like
> bit overkill. Of course if one could transform it into more generic
> cfengine packaging project, which would be the source for 
> FreeBSD ports,
> NetBSD pkgsrc, Debian's deb packages, ... 
> At the same time it would require that those systems maintainers would
> actually start using it, since it would be pointless (and probably
> confusing for users) to offer cfengine as package for platform xyz in
> savannah, while the platform xyz has separate maintainer for cfengine,
> whose packaging it in someother fashion.
> 
> What comes to generating cfengine RPM, there are pretty much two
> options. One is to provide spec file and leave it on that. Other
> solution requires that you have spec file, ~/.rpmmacros telling where
> your RPM building environment is and bunch of directory in 
> that building
> environment. Once all those are in place, you can build those packages
> with one single command and use another command to put GPG 
> signatures on
> them.
> 
> Unless your planning to use those RPM packages by yourself, 
> its probably
> safest to just distribute spec file and leave rest for admins, who
> locally deploy cfengine. I've attached Fedora's spec file for cfengine
> as attachment on this one. It builds cfengine and adds /etc/init.d
> scripts for cfexecd and cfservd (I guess I should add one for 
> cfenvd as
> well, but ...). If someone notices any errors in it, please file bugs
> into http://bugzilla.fedora.us/, so that we'll get them fixed.
> 
> -- 
> Juha Ylitalo       juha.o.ylitalo@nokia.com           <work e-mail>
> +358 40 562 6152   http://linux.nokia.com/~jylitalo/  <work www>
> 
>