[katello-devel] Checking in Gemfile.lock files

Dmitri Dolguikh dmitri at redhat.com
Thu Oct 25 15:01:22 UTC 2012


On 25/10/12 03:59 PM, David Davis wrote:
> I think we should add some new files to the project:
>
> src/gemfiles/Gemfilef16.lock
> src/gemfiles/Gemfilef17.lock
> src/gemfiles/Gemfilerhel6.lock
>
> That way, when I checkout the project, I can symlink in the Gemfile.lock for the system I am using:
>
> cd $KATELLO_HOME/src
> ln -s gemfiles/Gemfilef16.lock Gemfile.lock
>
> I think this has a lot of benefits:
>
> 1. We can still use rubygems and everyone on the same system will be using the same versions of the same gems. This ought to be the same as what's in the repos.
> 2. If someone updates the version of a gem, it has to be in the Gemfile.lock and it has to go through the same pull request process as the rest of our code. When we see a pull request that adds a new gem or updates a gem version, we can validate that the person has done the work to package it.
> 3. People don't have to use it if they don't want to, the project won't be shipped with a lock file by default, etc.
> 4. This helps to support different systems and there is a place in the project where I can check to see what gem version a system is using.
>
> Thanks.
>
> David
>
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel
I think this is a must, as f16/rhel6 and f17 will have different 
Gemfile.lock.

-d




More information about the katello-devel mailing list