mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Merge branch 'master' of ssh://git-annex.branchable.com

Browse source
This commit is contained in:
Joey Hess 2020-07-29 17:28:34 -04:00
commit 8200b52e12
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 8 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
doc/forum/standalone_tarballs_for_specific_versions/comment_11_543bb94e6a6c1313a09328402a191995._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="Ilya_Shlyakhter"
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
subject="version correspondence of standalone builds and official releases"
date="2020-07-29T15:36:37Z"
content="""
To answer @joeyh's question from a [related bug report](https://git-annex.branchable.com/bugs/kite_net_OSX__47__current__47___distribution_is_8.20200618_but_8.20200720.1_expected/#comment-06e9d73bdaff08d38d991ddc2b946f96) (\"maybe I'm missing something about how problematic the build being slightly behind until the next release is for you\"): it's problematic for [[conda-forge|install/conda]] packaging, because I want conda to install the non-standalone release if possible and automatically fall back on the standalone release if dependencies of the standard release conflict with other packages; for this to work, I need need the standalone release that corresponds to the same version as the standard release. I could package a standalone-only conda-forge release, marking it as an alpha to keep it from being preferred to the official release; but then there's no seamless fallback if the user wants the specific official version.
"""]]