Release/1.13.0

changelog.rst

@@ -18,10 +18,41 @@ Check https://github.com/conan-io/conan for issues and more details about develo
 
 .. important::
 
-    Conan 1.12 shouldn't break any existing 1.0 recipe or command line invocation. If it does, please submit a report on GitHub.
+    Conan 1.13 shouldn't break any existing 1.0 recipe or command line invocation. If it does, please submit a report on GitHub.
     Read more about the :ref:`Conan stability commitment<stability>`.
 
 
+1.13.0 (07-Mar-2019)
+--------------------
+
+- Feature: Added with_login parameter to tools.run_in_windows_bash() `#4673 <https://github.com/conan-io/conan/pull/4673>`_ . Docs `here <https://github.com/conan-io/docs/pull/1103>`__
+- Feature: The `deb` and `windows` Conan installers now use Python 3. `#4663 <https://github.com/conan-io/conan/pull/4663>`_
+- Feature: Allow configuring in *conan.conf* a different default ``package_id`` mode. `#4644 <https://github.com/conan-io/conan/pull/4644>`_ . Docs `here <https://github.com/conan-io/docs/pull/1106>`__
+- Feature: Apply Jinja2 to layout files before parsing them `#4596 <https://github.com/conan-io/conan/pull/4596>`_ . Docs `here <https://github.com/conan-io/docs/pull/1093>`__
+- Feature: Accept a PackageReference for the command  :command:`conan get` (argument `-p` is accepted, but hidden) `#4494 <https://github.com/conan-io/conan/pull/4494>`_ . Docs `here <https://github.com/conan-io/docs/pull/1070>`__
+- Feature: Re-implement Workspaces based on Editable packages. `#4481 <https://github.com/conan-io/conan/pull/4481>`_ . Docs `here <https://github.com/conan-io/docs/pull/1086>`__
+- Feature: Removed old "compatibility" mode of revisions. `#4462 <https://github.com/conan-io/conan/pull/4462>`_ . Docs `here <https://github.com/conan-io/docs/pull/1105>`__
+- Fix: When revisions enabled, add the revision to the json output of the info/install commands. `#4667 <https://github.com/conan-io/conan/pull/4667>`_
+- Fix: JSON output for `multi_config` now works in `install` and `create` commands `#4656 <https://github.com/conan-io/conan/pull/4656>`_
+- Fix: Deprecate 'cppflags' in favor of 'cxxflags' in class CppInfo `#4611 <https://github.com/conan-io/conan/pull/4611>`_ . Docs `here <https://github.com/conan-io/docs/pull/1091>`__
+- Fix: Return empty list if env variable is an empty string `#4594 <https://github.com/conan-io/conan/pull/4594>`_
+- Fix: `conan profile list` will now recursively list profiles. `#4591 <https://github.com/conan-io/conan/pull/4591>`_
+- Fix: `Instance of 'TestConan' has no 'install_folder' member` when exporting recipe `#4585 <https://github.com/conan-io/conan/pull/4585>`_
+- Fix: SCM replacement with comments below it `#4580 <https://github.com/conan-io/conan/pull/4580>`_
+- Fix: Remove package references associated to a remote in *registry.json* when that remote is deleted `#4568 <https://github.com/conan-io/conan/pull/4568>`_
+- Fix:  Fixed issue with Artifactory when the anonymous user is enabled, causing the uploads to fail without requesting the user and password. `#4526 <https://github.com/conan-io/conan/pull/4526>`_
+- Fix: Do not allow an alias to override an existing package `#4495 <https://github.com/conan-io/conan/pull/4495>`_
+- Fix: Do not display the warning when there are files in the package folder (#4438). `#4464 <https://github.com/conan-io/conan/pull/4464>`_
+- Bugfix: Solve problem with loading recipe python files in Python 3.7 because of ``module.__file__ = None`` `#4669 <https://github.com/conan-io/conan/pull/4669>`_
+- Bugfix: Do not attempt to upload non-existing packages, due to empty short_paths folders, or to explicit ``upload -p=id`` command. `#4615 <https://github.com/conan-io/conan/pull/4615>`_
+- Bugfix: Fix LIB overwrite in ``virtualbuildenv`` generator `#4583 <https://github.com/conan-io/conan/pull/4583>`_
+- Bugfix: Avoid ``str(self.settings.xxx)`` crash when the value is None. `#4571 <https://github.com/conan-io/conan/pull/4571>`_ . Docs `here <https://github.com/conan-io/docs/pull/1089>`__
+- Bugfix: Build-requires expand over the closure of the package they apply to, so they can create conflicts too. Previously, those conflicts were silently skipped, and builds would use an undetermined version and configuration of dependencies. `#4514 <https://github.com/conan-io/conan/pull/4514>`_
+- Bugfix: meson build type actually reflects recipe shared option `#4489 <https://github.com/conan-io/conan/pull/4489>`_
+- Bugfix: Fixed several bugs related to revisions. `#4462 <https://github.com/conan-io/conan/pull/4462>`_ . Docs `here <https://github.com/conan-io/docs/pull/1105>`__
+- Bugfix: Fixed several bugs related to the package `metadata.json` `#4462 <https://github.com/conan-io/conan/pull/4462>`_ . Docs `here <https://github.com/conan-io/docs/pull/1105>`__
+
+
 1.12.3 (18-Feb-2019)
 --------------------
 

conf.py

@@ -39,9 +39,9 @@
 ]
 
 # The short X.Y version.
-version = "1.12"
+version = "1.13"
 # The full version, including alpha/beta/rc tags.
-release = u'1.12.3'
+release = u'1.13.0'
 
 dir_path = os.path.dirname(os.path.realpath(__file__))
 if not os.path.exists(os.path.join(dir_path, "versions.json")):

creating_packages/define_abi_compatibility.rst

@@ -112,13 +112,12 @@ Let's try and check that it works properly when installing the package for GCC 4
 
 .. code-block:: bash
 
-    $ conan export myuser/mychannel
-    $ conan install Pkg/1.0@myuser/mychannel -s compiler=gcc -s compiler.version=4.5 ...
+    $ conan create . Pkg/1.0@myuser/mychannel -s compiler=gcc -s compiler.version=4.5 ...
 
     Requirements
         Pkg/1.0@myuser/mychannel from local
     Packages
-        Pkg/1.0@myuser/mychannel:mychannel:af044f9619574eceb8e1cca737a64bdad88246ad
+        Pkg/1.0@myuser/mychannel:af044f9619574eceb8e1cca737a64bdad88246ad
     ...
 
 We can see that the computed package ID is ``af04...46ad`` (not real). What happens if we specify GCC 4.6?
@@ -130,7 +129,7 @@ We can see that the computed package ID is ``af04...46ad`` (not real). What happ
     Requirements
         Pkg/1.0@myuser/mychannel from local
     Packages
-        Pkg/1.0@myuser/mychannel:mychannel:af044f9619574eceb8e1cca737a64bdad88246ad
+        Pkg/1.0@myuser/mychannel:af044f9619574eceb8e1cca737a64bdad88246ad
 
 The required package has the same result again ``af04...46ad``. Now we can try using GCC 4.4 (< 4.5):
 
@@ -141,7 +140,7 @@ The required package has the same result again ``af04...46ad``. Now we can try u
     Requirements
         Pkg/1.0@myuser/mychannel from local
     Packages
-        Pkg/1.0@myuser/mychannel:mychannel:7d02dc01581029782b59dcc8c9783a73ab3c22dd
+        Pkg/1.0@myuser/mychannel:7d02dc01581029782b59dcc8c9783a73ab3c22dd
 
 The computed package ID is different which means that we need a different binary package for GCC 4.4.
 
@@ -196,7 +195,9 @@ And the ``addition()`` function is called from the compiled *.cpp* files of ``My
 
 Then, **a new binary for MyLib/1.0 is required to be built for the new dependency version**. Otherwise it will maintain the old, buggy
 ``addition()`` version. Even in the case that ``MyLib/1.0`` doesn't have any change in its code lines neither in the recipe, the resulting
-binary rebuilding ``MyLib`` requires `MyOtherLib/2.1`` and the package to be different.
+binary rebuilding ``MyLib`` requires ``MyOtherLib/2.1`` and the package to be different.
+
+.. _package_id_mode:
 
 Using package_id() for Package Dependencies
 -------------------------------------------
@@ -265,6 +266,8 @@ You can determine if the following variables within any requirement change the I
 +-------------------------+----------+-----------------------------------------+----------+-------------+----------------+
 | **Modes / Variables**   | ``name`` | ``version``                             | ``user`` | ``channel`` | ``package_id`` |
 +=========================+==========+=========================================+==========+=============+================+
+| ``semver_direct_mode()``| Yes      | Yes, only > 1.0.0 (e.g., **1**.2.Z+b102)| No       | No          | No             |
++-------------------------+----------+-----------------------------------------+----------+-------------+----------------+
 | ``semver_mode()``       | Yes      | Yes, only > 1.0.0 (e.g., **1**.2.Z+b102)| No       | No          | No             |
 +-------------------------+----------+-----------------------------------------+----------+-------------+----------------+
 | ``major_mode()``        | Yes      | Yes (e.g., **1**.2.Z+b102)              | No       | No          | No             |
@@ -284,20 +287,65 @@ You can determine if the following variables within any requirement change the I
 | ``unrelated_mode()``    | No       | No                                      | No       | No          | No             |
 +-------------------------+----------+-----------------------------------------+----------+-------------+----------------+
 
-- ``semver_mode()``: This is the default mode. In this mode, only a major release version (starting from **1.0.0**) changes the package ID.
-  Every version change prior to 1.0.0 changes the package ID, but only major changes after 1.0.0 will be applied.
+All the modes can be applied to all dependencies, or to individual ones:
 
   .. code-block:: python
 
       def package_id(self):
+          # apply semver_mode for all the dependencies of the package
+          self.info.requires.semver_mode()
+          # use semver_mode just for MyOtherLib
           self.info.requires["MyOtherLib"].semver_mode()
 
+
+- ``semver_direct_mode()``: This is the default mode. It uses ``semver_mode()`` for direct dependencies (first
+  level dependencies, directly declared by the package) and ``unrelated_mode()`` for indirect, transitive
+  dependencies of the package. It assumes that the binary will be affected by the direct dependencies, which
+  they will already encode how their transitive dependencies affect them. This might not always be true, as
+  explained above, and that is the reason it is possible to customize it.
+
+  In this mode, if the package depends on "MyLib", which transitively depends on "MyOtherLib", the mode means:
+
+  .. code-block:: text
+
+    MyLib/1.2.3@user/testing       => MyLib/1.Y.Z
+    MyOtherLib/2.3.4@user/testing  =>
+
+  So the direct dependencies are mapped to the major version only. Changing its channel, or using version
+  ``MyLib/1.4.5`` will still produce ``MyLib/1.Y.Z`` and thus the same package-id.
+  The indirect, transitive dependency doesn't affect the package-id at all.
+
+- ``semver_mode()``: In this mode, only a major release version (starting from **1.0.0**) changes the package ID.
+  Every version change prior to 1.0.0 changes the package ID, but only major changes after 1.0.0 will be applied.
+
+  .. code-block:: python
+
+    def package_id(self):
+      self.info.requires["MyOtherLib"].semver_mode()
+
+  This results in:
+
+  .. code-block:: text
+
+    MyLib/1.2.3@user/testing       => MyLib/1.Y.Z
+    MyOtherLib/2.3.4@user/testing  => MyOtherLib/2.Y.Z
+
+  In this mode, versions starting with ``0`` are considered unstable and mapped to the full version:
+
+  .. code-block:: text
+
+    MyLib/0.2.3@user/testing       => MyLib/0.2.3
+    MyOtherLib/0.3.4@user/testing  => MyOtherLib/0.3.4
+
 - ``major_mode()``: Any change in the major release version (starting from **0.0.0**) changes the package ID.
 
   .. code-block:: python
 
-      def package_id(self):
-          self.info.requires["MyOtherLib"].major_mode()
+    def package_id(self):
+      self.info.requires["MyOtherLib"].major_mode()
+
+  This mode is basically the same as ``semver_mode``, but the only difference is that major versions ``0.Y.Z``,
+  which are considered unstable by semver, are still mapped to only the major, dropping the minor and patch parts.
 
 - ``minor_mode()``: Any change in major or minor (not patch nor build) version of the required dependency changes the package ID.
 
@@ -326,22 +374,39 @@ You can determine if the following variables within any requirement change the I
 
   .. code-block:: python
 
-      def package_id(self):
-          self.info.requires["MyOtherLib"].full_version_mode()
+    def package_id(self):
+      self.info.requires["MyOtherLib"].full_version_mode()
+
+  .. code-block:: text
+
+    MyOtherLib/1.3.4-a4+b3@user/testing  => MyOtherLib/1.3.4-a4+b3   
 
 - ``full_recipe_mode()``: Any change in the reference of the requirement (user & channel too) changes the package ID.
 
   .. code-block:: python
 
-      def package_id(self):
-          self.info.requires["MyOtherLib"].full_recipe_mode()
+    def package_id(self):
+      self.info.requires["MyOtherLib"].full_recipe_mode()
+
+  This keeps the whole dependency reference, except the package-id of the dependency.
+
+  .. code-block:: text
+
+    MyOtherLib/1.3.4-a4+b3@user/testing  => MyOtherLib/1.3.4-a4+b3@user/testing   
 
 - ``full_package_mode()``: Any change in the required version, user, channel or package ID changes the package ID.
 
   .. code-block:: python
 
-      def package_id(self):
-          self.info.requires["MyOtherLib"].full_package_mode()
+    def package_id(self):
+      self.info.requires["MyOtherLib"].full_package_mode()
+
+  This is the stricter mode. Any change to the dependency, including its binary package-id, will in turn
+  produce a new package-id for the consumer package.
+
+  .. code-block:: text
+
+    MyOtherLib/1.3.4-a4+b3@user/testing:73b..fa56  => MyOtherLib/1.3.4-a4+b3@user/testing:73b..fa56 
 
 - ``unrelated_mode()``: Requirements do not change the package ID.
 
@@ -377,10 +442,39 @@ The default behavior produces a *conaninfo.txt* that looks like:
 .. code-block:: text
 
     [requires]
-      MyOtherLib/2.Y.Z
+    MyOtherLib/2.Y.Z
 
     [full_requires]
-      MyOtherLib/2.2@demo/testing:73bce3fd7eb82b2eabc19fe11317d37da81afa56
+    MyOtherLib/2.2@demo/testing:73bce3fd7eb82b2eabc19fe11317d37da81afa56
+
+Changing the default package-id mode
+++++++++++++++++++++++++++++++++++++
+It is possible to change the default ``semver_direct_mode`` package-id mode, in the
+*conan.conf* file:
+
+.. code-block:: text
+   :caption: *conan.conf* configuration file
+
+   [general]
+   default_package_id_mode=full_package_mode
+
+Possible values are the names of the above methods: ``full_recipe_mode``, ``semver_mode``, etc.
+
+Note that the default package-id mode is the mode that is used when the package is initialized
+and **before** ``package_id()`` method is called. You can still define ``full_package_mode``
+as default in *conan.conf*, but if a recipe declare that it is header-only, with:
+
+  .. code-block:: python
+
+    def package_id(self):
+      self.info.header_only() # clears requires, but also settings if existing
+      # or if there are no settings/options, this would be equivalent
+      self.info.requires.clear() # or self.info.requires.unrelated_mode()
+
+That would still be executed, changing the "default" behavior, and leading to a package
+that only generates 1 package-id for all possible configurations and versions of dependencies.
+
+Remember that *conan.conf* can be shared and installed with :ref:`conan_config_install`.
 
 Library Types: Shared, Static, Header-only
 ++++++++++++++++++++++++++++++++++++++++++

deploy_gh_pages.py

@@ -99,7 +99,8 @@ def deploy():
     if should_deploy():
         config_git()
         clean_gh_pages()
-        versions_dict = {"master": "1.12",
+        versions_dict = {"master": "1.13",
+                         "release/1.12.3": "1.12",
                          "release/1.11.2": "1.11",
                          "release/1.10.2": "1.10",
                          "release/1.9.4": "1.9",