Issue #11864 has been updated by Daniel Pittman.

Status changed from In Topic Branch Pending Review to Closed

Darin Perusich wrote:
> Daniel Pittman wrote:
> > 
> > Darin, thanks for submitting this code.  It actually looks solid, and 
> > effective.  With everything you have done we could merge that into core.
> 
> Thanks! I've actually just made a number of modifications to it earlier today 
> removing all the `yum` specific crud that zypper ignores.

Awesome.

> > In view of that, would you still like to submit this for inclusion in the 
> > core of Puppet, or would you rather take it to the forge?
> 
> I can understand why you're moving these features/types/etc out of the puppet 
> core and into modules, it certainly makes updating and getting those modules 
> into peoples hands easier and quicker.

That is it: it means that people are not stuck for too long waiting for bugs to 
get fixed.  Nothing like knowing that 2.7.11 fixes your bug, and that you can't 
get it until you do lots of work, or your distro updates. :/

> While I haven't "played" with pluginsync yet, but from what I've read it's 
> nearly the equivalent to installing perl modules via CPAN or python egg's via 
> setuptools. Granted it doesn't pollute anything outside of 
> /etc/puppet/modules, this kind of "variable" stuff belong under 
> /var/lib/puppet IMO, which is slightly more palatable but you still lose 
> track of who/what owns the file because you can't query the packaging systems 
> about it.

On the server you can put anything you want in the module path, so if you 
prefer `/var/lib/puppet` you can totally hide them away there.

On the agents, where we copy that content down to, it lives in 
`/var/lib/puppet/lib` by default ... for exactly the reason you name. :)

> I realize this probably isn't something on your radar but it would be really 
> nice if there was a way to reference these additional types from the "type 
> reference" document. I know I almost never look at the forge for these things 
> and when I do it's always with a bit of skepticism.

I will pass that on to our web folks, and see if we can't figure out something 
useful to do there.  We are actively working to make the forge more awesome and 
all, because the counterpoint to "move stuff there" is "if it sucks, life sucks 
for our users", and ... well, our priority is the opposite of that. :)

Thank you again for the code.  That is awesome.

----------------------------------------
Feature #11864: zypper repository type
https://projects.puppetlabs.com/issues/11864

Author: Darin Perusich
Status: Closed
Priority: Normal
Assignee: Daniel Pittman
Category: package
Target version: 
Affected Puppet version: 2.7.9
Keywords: 
Branch: https://github.com/puppetlabs/puppet/pull/468


Hello,

Attached is a new type for describing zypper software repositories for 
OpenSUSE/SUSE systems, or any distribution using zypper for software 
management. It is a port of the 'yumrepo' repo type from the Puppet 2.7.9 code 
base.


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en.

Reply via email to