- From: Torben Knerr <
>
- To: "
" <
>
- Subject: [chef] Re: Re: Re: Re: Re: Re: Versioning forked cookbooks
- Date: Sun, 10 Aug 2014 21:30:32 +0200
There was once
https://tickets.opscode.com/browse/CHEF-4027 to support
SemVer with prerelease version identifiers, that would help in this
situation.
Not sure if it will ever come, though...
On Fri, Aug 8, 2014 at 10:38 PM, Andrew Brown
<
>
wrote:
>
Thank you!
>
>
On 2014-08-08, 3:44 PM, "Daniel DeLeo"
>
<
>
>
wrote:
>
>
>
>
>
>
>On Friday, August 8, 2014 at 12:42 PM, Mike wrote:
>
>
>
>> This is currently an unsolved problem.
>
>> There's a lot of contention around versioning and Chef, and there's no
>
>>clear workflow for "what works best".
>
>>
>
>> The flow Ranjib mentioned is one we do as well, and we don't freeze
>
>>cookbooks on upload for this reason.
>
>>
>
>> Is it perfect? Nope. But it works for now, at least until we can
>
>>introduce better version identifiers in to Chef, chef-client, knife, and
>
>>any plugins that we leverage for that to speak the same versioning
>
>>language.
>
>>
>
>> -M
>
>Not an immediate solution, but we¹re working on it. See
>
>https://github.com/opscode/chef-dk/blob/master/POLICYFILE_README.md and
>
>https://github.com/opscode/chef-rfc/pull/20
>
>
>
>--
>
>Daniel DeLeo
>
>
>
Archive powered by MHonArc 2.6.16.