James
James
> Hi @memsharded one question about this: we have conan recipes which determine dependencies depending on settings/options, so a lockfile 2.0 style only covering versions and revisions would still somehow...
> Hi @memsharded , thanks, so just to be sure I got it right: in the situation I describe above, where dependencies vary depending on settings or options, I would...
I am afraid not yet, this is a very early stage proof of concept, and there are still many unknown and high risks in this poc, so not anytime soon,...
@AbrilRBS @czoido I have pushed this a bit more, in case you want to have a look, or we can wait for reviewing together.
I have updated this PR with the latest ``develop2`` branch, completed some tests and fixed a couple of bugs. If there is interest in moving this forward, it would be...
Hi @alin-avasilcutei Yes, it is not possible to store the lockfile in the export folder in the general case: - Lockfiles need to lock different configurations, for different binaries that...
There is a ticket in the purl-spec org to check with the experts there: https://github.com/package-url/purl-spec/issues/705
Hi @timpatt Thanks for your report. > We use an internal Artifactory server that mirrors conancenter and I've noticed a strange difference between the two when running conan list qt/6.8.3:*...
Hi @timpatt That clarifies the issue. That is an issue in the server side, that is corrupting the packages. - 6.8.3 - _ - 60506664b... (etc) - e58b26c408... #This folder...
I am re-opening this ticket to track it on our side too.