[Puppet Users] Re: how to update solaris packages without keeping local copies

2008-10-28 Thread Ohad Levy
o drag in dependencies that pollute our > dev > > > environments so we can't use them in most cases.) > > > > > > Matt > > > > > > > -----Original Message- > > > > From: puppet-users@googlegroups.com > > > [mailto:[EMAIL PR

[Puppet Users] Re: how to update solaris packages without keeping local copies

2008-10-27 Thread Matt McLeod
es that pollute our dev > > environments so we can't use them in most cases.) > > > > Matt > > > > > -Original Message- > > > From: puppet-users@googlegroups.com > > [mailto:[EMAIL PROTECTED] > > > On Behalf Of Ohad Levy > >

[Puppet Users] Re: how to update solaris packages without keeping local copies

2008-10-27 Thread Ohad Levy
ironments so we can't use them in most cases.) >> >> Matt >> >> > -Original Message- >> > From: puppet-users@googlegroups.com >> [mailto:[EMAIL PROTECTED] >> > On Behalf Of Ohad Levy >> > Sent: Tuesday, 28 October 2008 1:09 PM &g

[Puppet Users] Re: how to update solaris packages without keeping local copies

2008-10-27 Thread Ohad Levy
s that pollute our dev > environments so we can't use them in most cases.) > > Matt > > > -Original Message- > > From: puppet-users@googlegroups.com > [mailto:[EMAIL PROTECTED] > > On Behalf Of Ohad Levy > > Sent: Tuesday, 28 October 2008 1:09 P

[Puppet Users] Re: how to update solaris packages without keeping local copies

2008-10-27 Thread McLeod, Matt
M > To: puppet-users@googlegroups.com > Subject: [Puppet Users] Re: how to update solaris packages without keeping > local copies > > Why not to create your own blastwave repo to use pkg-get with, or am I > missing anything here? > > Thanks, > Ohad > > >

[Puppet Users] Re: how to update solaris packages without keeping local copies

2008-10-27 Thread Ohad Levy
Why not to create your own blastwave repo to use pkg-get with, or am I missing anything here? Thanks, Ohad On Tue, Oct 28, 2008 at 8:41 AM, McLeod, Matt <[EMAIL PROTECTED]> wrote: > Sam Rowe wrote: > > Another quick point about this.. pkgadd isn't smart enough to handle a > > response file with

[Puppet Users] Re: how to update solaris packages without keeping local copies

2008-10-27 Thread McLeod, Matt
Sam Rowe wrote: > Another quick point about this.. pkgadd isn't smart enough to handle a > response file with packages installed this way. It will however use an admin file. Here's what I have for installing packages on Solaris systems: define pkgadd { $pkgrepo="http://pca.itgasiapac.com

[Puppet Users] Re: how to update solaris packages without keeping local copies

2008-10-21 Thread Sam Rowe
On Thu, Oct 16, 2008 at 3:41 AM, martin <[EMAIL PROTECTED]> wrote: > > Richard, > > On Oct 16, 1:47 am, Richard Doty <[EMAIL PROTECTED]> wrote: >> I have a solaris package stored on a puppet server. I'd like >> to be able to maintain the package on a client system without >> having to also keep a

[Puppet Users] Re: how to update solaris packages without keeping local copies

2008-10-16 Thread Peter Meier
Hi > it is not very well known, but pkgadd can take an URL as dtastream, > i.e. > pkgadd -d http://yourserver.com/pkgs/SUNWxyz.pkg > > I haven't checked if puppet supports this, but it is worth > investigating :) for all other package providers I use, you can use the source param to install pa

[Puppet Users] Re: how to update solaris packages without keeping local copies

2008-10-16 Thread martin
Richard, On Oct 16, 1:47 am, Richard Doty <[EMAIL PROTECTED]> wrote: > I have a solaris package stored on a puppet server.  I'd like > to be able to maintain the package on a client system without > having to also keep a copy of the package file on the client > system.  (think lots and lots of pa

[Puppet Users] Re: how to update solaris packages without keeping local copies

2008-10-15 Thread Ohad Levy
you could create a repository based on pkg-get binary (blastwave). Cheers, Ohad On Thu, Oct 16, 2008 at 7:47 AM, Richard Doty <[EMAIL PROTECTED]> wrote: > > Greetings, > > I have a solaris package stored on a puppet server. I'd like > to be able to maintain the package on a client system withou