Re: [Puppet-dev] appeal for advice re: pip provider, multiple packages with same name, etc.

2014-01-22 Thread David Schmitt
On 21.01.2014 19:20, Andy Parker wrote: I think that what we are hitting here is just a limitation of puppet's ability to describe systems. What I think is missing is any idea of an independent container. Within a given container everything needs to be unique, but between containers you can have

Re: [Puppet-dev] appeal for advice re: pip provider, multiple packages with same name, etc.

2014-01-21 Thread Andy Parker
On Sat, Jan 18, 2014 at 8:17 AM, Felix Frank < felix.fr...@alumni.tu-berlin.de> wrote: > Hi, > > fascinating discussion. I think I can amend to Jason's point of view. > > On 01/15/2014 04:25 AM, Jason Antman wrote: > > it loses Puppet's native ability to > > log and report on changes to individual

Re: [Puppet-dev] appeal for advice re: pip provider, multiple packages with same name, etc.

2014-01-18 Thread Felix Frank
Hi, fascinating discussion. I think I can amend to Jason's point of view. On 01/15/2014 04:25 AM, Jason Antman wrote: > it loses Puppet's native ability to > log and report on changes to individual resources. The ability to easily > see when a given package is upgraded, or what version it's at, a

Re: [Puppet-dev] appeal for advice re: pip provider, multiple packages with same name, etc.

2014-01-15 Thread Dustin J. Mitchell
Hah, so I was looking in the wrong mail account. I'm glad I'm not going crazy! I agree with all of the limitations you've outlined. I don't see any good fixes, sadly, but hopefully someone else does. Dustin -- You received this message because you are subscribed to the Google Groups "Puppet

Re: [Puppet-dev] appeal for advice re: pip provider, multiple packages with same name, etc.

2014-01-14 Thread Jason Antman
Dustin, Yeah, you sure have. I reached out to the puppetagain/releng list (and maybe also puppet-users) a few months ago when I first started this project. Your advice was probably pretty much the same, so I hope my replies are. On 01/14/2014 09:25 PM, Dustin J. Mitchell wrote: > I could have swo

Re: [Puppet-dev] appeal for advice re: pip provider, multiple packages with same name, etc.

2014-01-14 Thread Dustin J. Mitchell
I could have sworn I've said some of this before, but I'm not sure where. So sorry if this is repetitive. First, I think what your implementation is missing is a resource name that's globally unique to the host. Let's say I want to install different versions of sqlalchemy in /venvs/staging and /

[Puppet-dev] appeal for advice re: pip provider, multiple packages with same name, etc.

2014-01-14 Thread Jason Antman
Greetings, oh wizards of puppet internals. (and other titles and salutations as appropriate) I've been doing some work lately on the `pip` package provider and, despite some assistance on my PR (https://github.com/puppetlabs/puppet/pull/2170) and IRC, I think I've hit a brick wall. ( Aside, For t