consuming conan latest version












0















We are working on integration of conan package management into our pipeline.



Our conan package are store in Artifactory.



The convention of our version numbers looks like this:




Minor.Major.Patch-BuildVerison




As we know, for consuming the latest version, need to use




[> Minor.Major.Patch]




into the conanfile.py.



The only way we were able to get a latest version from versions like our convention is to write it like this:




[> Minor.Major.Patch-0]




But our problem happens in situations like the example below:



Let's say these are the version numbers of a package that we try to consume it's latest version:




1.2.3-1



1.2.3-2



1.2.3-3




if we write in our conanfile.py




[>1.2.3-0]




we will get the




1.2.3-3




as well.



But if we upload the version




1.2.4-1




of thus package (only update the Patch number), and we leave the conanfile.py as is - we will still get the




1.2.3-3




not the




1.2.4-1




as accepted.



Please help us know what is the best way to get what we want.



Thanks.










share|improve this question























  • Follow up github issue: github.com/conan-io/conan/issues/3997

    – drodri
    Nov 25 '18 at 23:24











  • Thanks, but it's my issue

    – Yos
    Nov 26 '18 at 5:07
















0















We are working on integration of conan package management into our pipeline.



Our conan package are store in Artifactory.



The convention of our version numbers looks like this:




Minor.Major.Patch-BuildVerison




As we know, for consuming the latest version, need to use




[> Minor.Major.Patch]




into the conanfile.py.



The only way we were able to get a latest version from versions like our convention is to write it like this:




[> Minor.Major.Patch-0]




But our problem happens in situations like the example below:



Let's say these are the version numbers of a package that we try to consume it's latest version:




1.2.3-1



1.2.3-2



1.2.3-3




if we write in our conanfile.py




[>1.2.3-0]




we will get the




1.2.3-3




as well.



But if we upload the version




1.2.4-1




of thus package (only update the Patch number), and we leave the conanfile.py as is - we will still get the




1.2.3-3




not the




1.2.4-1




as accepted.



Please help us know what is the best way to get what we want.



Thanks.










share|improve this question























  • Follow up github issue: github.com/conan-io/conan/issues/3997

    – drodri
    Nov 25 '18 at 23:24











  • Thanks, but it's my issue

    – Yos
    Nov 26 '18 at 5:07














0












0








0








We are working on integration of conan package management into our pipeline.



Our conan package are store in Artifactory.



The convention of our version numbers looks like this:




Minor.Major.Patch-BuildVerison




As we know, for consuming the latest version, need to use




[> Minor.Major.Patch]




into the conanfile.py.



The only way we were able to get a latest version from versions like our convention is to write it like this:




[> Minor.Major.Patch-0]




But our problem happens in situations like the example below:



Let's say these are the version numbers of a package that we try to consume it's latest version:




1.2.3-1



1.2.3-2



1.2.3-3




if we write in our conanfile.py




[>1.2.3-0]




we will get the




1.2.3-3




as well.



But if we upload the version




1.2.4-1




of thus package (only update the Patch number), and we leave the conanfile.py as is - we will still get the




1.2.3-3




not the




1.2.4-1




as accepted.



Please help us know what is the best way to get what we want.



Thanks.










share|improve this question














We are working on integration of conan package management into our pipeline.



Our conan package are store in Artifactory.



The convention of our version numbers looks like this:




Minor.Major.Patch-BuildVerison




As we know, for consuming the latest version, need to use




[> Minor.Major.Patch]




into the conanfile.py.



The only way we were able to get a latest version from versions like our convention is to write it like this:




[> Minor.Major.Patch-0]




But our problem happens in situations like the example below:



Let's say these are the version numbers of a package that we try to consume it's latest version:




1.2.3-1



1.2.3-2



1.2.3-3




if we write in our conanfile.py




[>1.2.3-0]




we will get the




1.2.3-3




as well.



But if we upload the version




1.2.4-1




of thus package (only update the Patch number), and we leave the conanfile.py as is - we will still get the




1.2.3-3




not the




1.2.4-1




as accepted.



Please help us know what is the best way to get what we want.



Thanks.







version conan






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 25 '18 at 13:58









YosYos

114




114













  • Follow up github issue: github.com/conan-io/conan/issues/3997

    – drodri
    Nov 25 '18 at 23:24











  • Thanks, but it's my issue

    – Yos
    Nov 26 '18 at 5:07



















  • Follow up github issue: github.com/conan-io/conan/issues/3997

    – drodri
    Nov 25 '18 at 23:24











  • Thanks, but it's my issue

    – Yos
    Nov 26 '18 at 5:07

















Follow up github issue: github.com/conan-io/conan/issues/3997

– drodri
Nov 25 '18 at 23:24





Follow up github issue: github.com/conan-io/conan/issues/3997

– drodri
Nov 25 '18 at 23:24













Thanks, but it's my issue

– Yos
Nov 26 '18 at 5:07





Thanks, but it's my issue

– Yos
Nov 26 '18 at 5:07












1 Answer
1






active

oldest

votes


















0














Conan v.1.10 introduced two new options associated with version ranges (from the docs):





  • loose: to include/exclude valid semver string checking (defaulted to True)


  • include_prerelease: to include/exclude prerelease versions in the search range (defaulted to False)


Use these options to have more fine-grained control over requirements:



class HelloConan(ConanFile):
requires = "Pkg/[~1.2.3,loose=False,include_prerelease=True]@user/stable"





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%2f53468228%2fconsuming-conan-latest-version%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









    0














    Conan v.1.10 introduced two new options associated with version ranges (from the docs):





    • loose: to include/exclude valid semver string checking (defaulted to True)


    • include_prerelease: to include/exclude prerelease versions in the search range (defaulted to False)


    Use these options to have more fine-grained control over requirements:



    class HelloConan(ConanFile):
    requires = "Pkg/[~1.2.3,loose=False,include_prerelease=True]@user/stable"





    share|improve this answer




























      0














      Conan v.1.10 introduced two new options associated with version ranges (from the docs):





      • loose: to include/exclude valid semver string checking (defaulted to True)


      • include_prerelease: to include/exclude prerelease versions in the search range (defaulted to False)


      Use these options to have more fine-grained control over requirements:



      class HelloConan(ConanFile):
      requires = "Pkg/[~1.2.3,loose=False,include_prerelease=True]@user/stable"





      share|improve this answer


























        0












        0








        0







        Conan v.1.10 introduced two new options associated with version ranges (from the docs):





        • loose: to include/exclude valid semver string checking (defaulted to True)


        • include_prerelease: to include/exclude prerelease versions in the search range (defaulted to False)


        Use these options to have more fine-grained control over requirements:



        class HelloConan(ConanFile):
        requires = "Pkg/[~1.2.3,loose=False,include_prerelease=True]@user/stable"





        share|improve this answer













        Conan v.1.10 introduced two new options associated with version ranges (from the docs):





        • loose: to include/exclude valid semver string checking (defaulted to True)


        • include_prerelease: to include/exclude prerelease versions in the search range (defaulted to False)


        Use these options to have more fine-grained control over requirements:



        class HelloConan(ConanFile):
        requires = "Pkg/[~1.2.3,loose=False,include_prerelease=True]@user/stable"






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Dec 28 '18 at 13:04









        jgsogojgsogo

        164311




        164311
































            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%2f53468228%2fconsuming-conan-latest-version%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

            Create new schema in PostgreSQL using DBeaver

            Deepest pit of an array with Javascript: test on Codility

            Costa Masnaga