Why does `bundle update rack` vendor millions of lines of code?












1















For a security patch, I needed to update the rack gem, so I ran this:



bundle update rack



It took a while, and at the end I see this new folder /vendor/cache/ruby/2.4.0/ and it contains 2.7 million lines of code.



This really doesn't seem right. Does anyone know what's happening? I tried to delete that folder, but when I ran rails console after that a message said I needed to run bundle install, which put all the contents back in that mammoth folder.










share|improve this question























  • What's the output of bundle env and/or cat .bundle/config? I suspect that you've vendor'd your gems.

    – Gavin Miller
    Nov 21 '18 at 1:08











  • .bundle/config is BUNDLE_CACHE_ALL: "true" BUNDLE_PATH: "vendor/cache"

    – Mirror318
    Nov 21 '18 at 1:20
















1















For a security patch, I needed to update the rack gem, so I ran this:



bundle update rack



It took a while, and at the end I see this new folder /vendor/cache/ruby/2.4.0/ and it contains 2.7 million lines of code.



This really doesn't seem right. Does anyone know what's happening? I tried to delete that folder, but when I ran rails console after that a message said I needed to run bundle install, which put all the contents back in that mammoth folder.










share|improve this question























  • What's the output of bundle env and/or cat .bundle/config? I suspect that you've vendor'd your gems.

    – Gavin Miller
    Nov 21 '18 at 1:08











  • .bundle/config is BUNDLE_CACHE_ALL: "true" BUNDLE_PATH: "vendor/cache"

    – Mirror318
    Nov 21 '18 at 1:20














1












1








1








For a security patch, I needed to update the rack gem, so I ran this:



bundle update rack



It took a while, and at the end I see this new folder /vendor/cache/ruby/2.4.0/ and it contains 2.7 million lines of code.



This really doesn't seem right. Does anyone know what's happening? I tried to delete that folder, but when I ran rails console after that a message said I needed to run bundle install, which put all the contents back in that mammoth folder.










share|improve this question














For a security patch, I needed to update the rack gem, so I ran this:



bundle update rack



It took a while, and at the end I see this new folder /vendor/cache/ruby/2.4.0/ and it contains 2.7 million lines of code.



This really doesn't seem right. Does anyone know what's happening? I tried to delete that folder, but when I ran rails console after that a message said I needed to run bundle install, which put all the contents back in that mammoth folder.







ruby-on-rails bundler






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 21 '18 at 0:43









Mirror318Mirror318

5,05122943




5,05122943













  • What's the output of bundle env and/or cat .bundle/config? I suspect that you've vendor'd your gems.

    – Gavin Miller
    Nov 21 '18 at 1:08











  • .bundle/config is BUNDLE_CACHE_ALL: "true" BUNDLE_PATH: "vendor/cache"

    – Mirror318
    Nov 21 '18 at 1:20



















  • What's the output of bundle env and/or cat .bundle/config? I suspect that you've vendor'd your gems.

    – Gavin Miller
    Nov 21 '18 at 1:08











  • .bundle/config is BUNDLE_CACHE_ALL: "true" BUNDLE_PATH: "vendor/cache"

    – Mirror318
    Nov 21 '18 at 1:20

















What's the output of bundle env and/or cat .bundle/config? I suspect that you've vendor'd your gems.

– Gavin Miller
Nov 21 '18 at 1:08





What's the output of bundle env and/or cat .bundle/config? I suspect that you've vendor'd your gems.

– Gavin Miller
Nov 21 '18 at 1:08













.bundle/config is BUNDLE_CACHE_ALL: "true" BUNDLE_PATH: "vendor/cache"

– Mirror318
Nov 21 '18 at 1:20





.bundle/config is BUNDLE_CACHE_ALL: "true" BUNDLE_PATH: "vendor/cache"

– Mirror318
Nov 21 '18 at 1:20












1 Answer
1






active

oldest

votes


















1














At some point you've ran bundle install --path=vendor/cache. This vendors everything into vendor/cache as implied.



To reverse this, you can simply delete the line from the .bundle/config file, and delete the vendor/cache folder. Re-run bundle update rack and everything should be cleaned up nicely.






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53403742%2fwhy-does-bundle-update-rack-vendor-millions-of-lines-of-code%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    At some point you've ran bundle install --path=vendor/cache. This vendors everything into vendor/cache as implied.



    To reverse this, you can simply delete the line from the .bundle/config file, and delete the vendor/cache folder. Re-run bundle update rack and everything should be cleaned up nicely.






    share|improve this answer




























      1














      At some point you've ran bundle install --path=vendor/cache. This vendors everything into vendor/cache as implied.



      To reverse this, you can simply delete the line from the .bundle/config file, and delete the vendor/cache folder. Re-run bundle update rack and everything should be cleaned up nicely.






      share|improve this answer


























        1












        1








        1







        At some point you've ran bundle install --path=vendor/cache. This vendors everything into vendor/cache as implied.



        To reverse this, you can simply delete the line from the .bundle/config file, and delete the vendor/cache folder. Re-run bundle update rack and everything should be cleaned up nicely.






        share|improve this answer













        At some point you've ran bundle install --path=vendor/cache. This vendors everything into vendor/cache as implied.



        To reverse this, you can simply delete the line from the .bundle/config file, and delete the vendor/cache folder. Re-run bundle update rack and everything should be cleaned up nicely.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 21 '18 at 1:28









        Gavin MillerGavin Miller

        33.7k18106169




        33.7k18106169






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53403742%2fwhy-does-bundle-update-rack-vendor-millions-of-lines-of-code%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Can a sorcerer learn a 5th-level spell early by creating spell slots using the Font of Magic feature?

            Does disintegrating a polymorphed enemy still kill it after the 2018 errata?

            A Topological Invariant for $pi_3(U(n))$