The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Feature #4918

Should be able to generate srpm and rpm from git checkout using rake

Added by Michael Stahnke over 3 years ago. Updated over 2 years ago.

Status:Needs DecisionStart date:10/02/2010
Priority:NormalDue date:
Assignee:Michael Stahnke% Done:

0%

Category:-
Target version:-
Affected Puppet version: Branch:
Keywords:rake rpm spec communitypatch

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This ticket may be automatically exported to the PUP project on JIRA using the button below:


Description

As a user with a security policy that provides limited source for package downloads, in order to have a packaged version of puppet, packages should be able to be generated through a git clone and rake.

There was some discussion about this earlier this week or last in #puppet. It would be nice to have a rake task to generate an rpm from the contributed spec file provided by tmz. This would allow people who would like rpms from upstream to have an even easier time making their own.

Patch forthcoming.

History

#1 Updated by Michael Stahnke over 3 years ago

I sent a patch to the mailing list. Not exactly sure what the correct way to link that in here would be.

#2 Updated by Matt Robinson over 3 years ago

  • Status changed from Unreviewed to In Topic Branch Pending Review
  • Target version set to 52
  • Keywords changed from rake rpm spec to rake rpm spec communitypatch

Michael, thanks for the patch. Sending to the mailing list was the right thing. If you have a github branch (eg http://github.com/yourgithubid/puppet/tree/ticket/2.6.x/4918) please also add it to this ticket in the branch field. There’s info on branch naming conventions here: http://projects.puppetlabs.com/projects/puppet/wiki/Development_Development_Lifecycle

#3 Updated by Michael Stahnke over 3 years ago

http://github.com/stahnma/puppet/tree/tickets/master/4918

I think I don’t have rights to update the branch field or any of the original ticket any more

#4 Updated by Todd Zullinger over 3 years ago

Nice. I’ll try to play with this soon too.

#5 Updated by Matt Robinson over 3 years ago

  • Status changed from In Topic Branch Pending Review to Needs Decision
  • Assignee set to James Turnbull

James, I’m assigning this to you as we discussed in person. I wanted your feedback on putting rake tasks in to build packages and whether this was something we wanted to do.

#6 Updated by Matt Robinson over 3 years ago

Hey James, have you had a chance to look at the patch or think about including rake tasks for building packages?

#7 Updated by James Turnbull over 3 years ago

I have not.

#8 Updated by Michael Stahnke over 3 years ago

I got some pointers/comments from tmz on the dev list that I’d like to put into this patch anyway, I just haven’t had much time to get back to it. The current patch certainly works, but some of Todd’s ideas enhance the overall outcome.

#9 Updated by Matt Robinson over 3 years ago

  • Assignee changed from James Turnbull to Nigel Kersten

Hey Nigel, thought I’d see if you had an opinion about adding rake tasks to puppet to build packages. This probably needs further thought based on the work that’s being done on Puppet Enterprise and however they’re doing packaging.

#10 Updated by Nigel Kersten over 3 years ago

  • Status changed from Needs Decision to Accepted
  • Assignee deleted (Nigel Kersten)

I think it’s perfectly reasonable. We should also convert the conf/osx/createpackage.sh script to a rake task.

#11 Updated by James Turnbull about 3 years ago

  • Target version deleted (52)

#12 Updated by Nigel Kersten over 2 years ago

  • Status changed from Accepted to Needs Decision
  • Assignee set to Michael Stahnke

Mike, this one needs your decision I think. I’m in favor, but it’s your area.

Also available in: Atom PDF