[chef] Re: Re: Re: Re: Re: ark cookbook resources are not idempotent?

[Sean OMeara < >]

RIght now its using Chef::Config[:file_cache_path] 

.... send a patch it maybe?

I don't have bandwidth this week and feel funny filing a ticket against something thats not released yet as a reminder to myself to fix it =)

-s

On Tue, May 21, 2013 at 8:07 AM, Mike < " target="_blank"> > wrote:

The temp dir should probably be /var/cache/chef or /var/chef/cache
(why are there two???).

It probably already is, however in my vagrant box it's
/tmp/vagrant-chef-1/ so I don't expect it to be there all the time.

Thanks for thinking about it.

On Tue, May 21, 2013 at 6:21 AM, Sean OMeara < "> > wrote:

> hrm... maybe we can dedicate a temp directory for ark?
>
> Personally, I'd rather see the arks being downloaded and checksummed with an
> extraction trigger than using a "if the directory exists" test because its
> stronger.
>
> The real solution to this is "use packages"
>
> -s
>
>
> On Mon, May 20, 2013 at 8:52 PM, Mike < "> > wrote:
>>
>> Trying ark 0.1.1 from master.
>>
>> I can confirm that the behavior I was unhappy with seems to be
>> resolved, thanks Joshua & Sean!
>>
>> This issue may predate the current state, but I found it nonetheless:
>>
>> ark resource downloads source file despite being installed, probably
>> due to the temp dir being devoid of the file.
>> How do we prevent a download of something that's already been installed?
>> Maybe use other attributes provided to determine if the
>> 'package-version' is already there and not empty?
>>
>> -M
>>
>>
>> On Mon, May 20, 2013 at 12:56 PM, Joshua Timberman < "> >
>> wrote:
>> > Hi Mike,
>> >
>> > Can you try with the master branch of the ark cookbook git repository?
>> > We've recently refactored it pretty heavily to use inline resources in the
>> > provider.
>> >
>> > See COOK-2520 for more information.
>> >
>> > On May 20, 2013, at 6:16 AM, Mike < "> > wrote:
>> >
>> >> I've started looking at using ark to do the download, unzip,
>> >> configure, make, make install dance.
>> >>
>> >> It seems like every time Chef runs, `make`, `make install` is executed
>> >> again.
>> >>
>> >> ark 'ghostscript' do
>> >>  url 'http://downloads.ghostscript.com/public/ghostscript-9.07.tar.gz'
>> >>  version '9.07'
>> >>  checksum
>> >> '44800d004c53f13192d1b5db413119198ddfc8a11c4d2a030aac2f2fda822ebf'
>> >>  action [:configure, :install_with_make]
>> >> end
>> >>
>> >> From logs:
>> >>
>> >>  * ark[ghostscript] action install_with_makeRecipe: <Dynamically
>> >> Defined Resource>
>> >>  * directory[/usr/local/ghostscript-9.07] action create (up to date)
>> >>  * bash[build with make] action run
>> >>    - execute "bash"  "/tmp/chef-script20130520-15167-13q0blu"
>> >>
>> >>  * link[/usr/local/ghostscript] action create (up to date)
>> >>  * bash[make install] action run
>> >>    - execute "bash"  "/tmp/chef-script20130520-15167-ys05zc"
>> >>
>> >> Chef 11.4.4, Omnibus build, ark 0.1.0
>> >>
>> >> Further evidenced by the timestamp on every binary added getting a new
>> >> timestamp.
>> >>
>> >> Is this just me? I hope not...
>> >> -M
>> >
>
>