[Puppet Users] Release tarball spec file
I know this is a crazy request, but I was kind of wondering why it was so
hard for Puppet Labs to maintain the RPM spec file that comes contained in
the release tarball, so that modifications weren't required to actually get
it to build. Crazy huh?
For example, the SPEC file contains this...
Version:2.7.2
Release:0.2.rc1%{?dist}
but the release is 2.7.3. Also 'rc1' is hard coded in several places, and so
forth.
Doug
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Release tarball spec file
On Wed, Aug 24, 2011 at 10:16 AM, Douglas Garstang doug.garst...@gmail.com wrote: I know this is a crazy request, but I was kind of wondering why it was so hard for Puppet Labs to maintain the RPM spec file that comes contained in the release tarball, so that modifications weren't required to actually get it to build. Crazy huh? https://projects.puppetlabs.com/issues/9016 was raised on this issue as well. See my comments in the ticket. The basic premise is that I'd like to remove all packaging content from Puppet as a project. The packaging content is not what upstream is. Puppet is released as a tarball and a gem. From there it can be packaged. We (Puppet Labs) plan to provide (better) packages in the near future. I know I keep saying that, but I've been very busy with some other workloads. I'd like to move the packaging bits into a separate, but completely open project. Of course Linux and BSD distribution still may do their own packaging of Puppet as well. As for why it's difficult to update spec files and the like, when we have an RC, I prefer to cut that *exact* content as the final. Basically, from the same tag. If I update specs and such, it changes to content. I'm open to ideas on making it better. Mike -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Release tarball spec file
Douglas Garstang wrote:
I know this is a crazy request, but I was kind of wondering why it was
so hard for Puppet Labs to maintain the RPM spec file that comes
contained in the release tarball, so that modifications weren't required
to actually get it to build. Crazy huh?
For example, the SPEC file contains this...
Version:2.7.2
Release:0.2.rc1%{?dist}
but the release is 2.7.3. Also 'rc1' is hard coded in several places,
and so forth.
Douglas
Patches are always welcome. If you update it or change it then send a
pull request and it'll be more likely to be up-to-date.
That being said I echo Mike's comments about it being a helper for
people rather than our primary role as the upstream developer. My
preference is we focus on features and fixes rather than packaging
specification that is actually better handled by people downstream of us.
Regards
James Turnbull
--
James Turnbull
Puppet Labs
1-503-734-8571
Join us for PuppetConf http://www.bit.ly/puppetconfsig, September 22nd
and 23rd in Portland, Oregon, USA.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
