Re: Relying on $PATH in RPM scriplets + little bit of marketing

2013-08-01 Thread Mathieu Bridon
On Thu, 2013-08-01 at 10:13 +0200, Lukas Zapletal wrote: > On Thu, Aug 01, 2013 at 10:06:15AM +0200, Lukas Zapletal wrote: > > Which reminds me - are we prepared from the marketing perspective? I can > > imagine Phoronix.com to publish an article "Red Hat reaches million > > bugs". We should have s

Re: Relying on $PATH in RPM scriplets + little bit of marketing

2013-08-01 Thread Lukas Zapletal
On Thu, Aug 01, 2013 at 10:06:15AM +0200, Lukas Zapletal wrote: > Which reminds me - are we prepared from the marketing perspective? I can > imagine Phoronix.com to publish an article "Red Hat reaches million > bugs". We should have some PR prepared explaining that we track features > there (I can

Re: Relying on $PATH in RPM scriplets + little bit of marketing

2013-08-01 Thread Lukas Zapletal
On Fri, Jul 26, 2013 at 06:00:04PM +0100, Richard Jones wrote: > IMHO there's probably a case for filing a bug with upstream cloud-init > and getting them to drop something like: > > Environment=PATH=[some predictable path] > > into cloud-init-0.7.2/systemd/cloud-*.service. Oh, good point. Tha

Re: Relying on $PATH in RPM scriplets

2013-07-26 Thread Richard W.M. Jones
On Fri, Jul 26, 2013 at 06:06:00PM +0200, Lukas Zapletal wrote: > Hey, > > since we provide cloud images starting with Fedora 19, I noticed that > cloud-init, which is used in these, does not execute user shell scripts > with $PATH set properly which is causing issues for packages that does > not

Relying on $PATH in RPM scriplets

2013-07-26 Thread Lukas Zapletal
Hey, since we provide cloud images starting with Fedora 19, I noticed that cloud-init, which is used in these, does not execute user shell scripts with $PATH set properly which is causing issues for packages that does not provide full paths in scriplets. I know we have some examples which relies