Hi, The 'corruption' we've seen is that at times it doesn't properly pick up the files to concat from. I must admit that this wasn't with your concat module but the one we used at work. ( R.I. Pienaar; eCG should ring a bell i think? )
Op dinsdag 18 december 2012 10:20:22 UTC+1 schreef R.I. Pienaar het volgende: > > > > ----- Original Message ----- > > From: "Richard Pijnenburg" <[email protected] <javascript:>> > > To: [email protected] <javascript:> > > Sent: Tuesday, December 18, 2012 7:59:53 AM > > Subject: Re: [Puppet-dev] file concat library > > > > The main benefit is that it doesn't work with temp files and an, in > > my opinion, ugly exec construct. > > I agree the exec is hacky, a native one would be great. > > > Other benefit is that because it doesn't work with temp files it > > won't corrupt the concating of files what fails at times, and you > > can you explain how this corruption happens? I've not had even a single > report of such corruption with the concat library > > > > Erik Dalén: One benefit of ripieenar's non native one though is that it creates a file resource for the destination file, so if you try to create another file resource for that file you get a proper duplicate resource declaration error. Is there any way to implement that > protection with a native resource like this? Natively it uses the file resource code and should give a duplicate resource deceleration when wanting to write the same file. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-dev/-/kf-qcb2690kJ. 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-dev?hl=en.
