Open averissimo opened 11 months ago
(moving discussion from chat to issue @pawelru)
I've already tested a solution of 1.
: That would create some clutter.
However, there's a positive side-effect as it would make the max
strategy more effective, as it would use pkg.c
/teal.data
development version.
I personally leaning towards 2. This would be a clean solution because something wrong is with pkg.b
hence any fixes needs to be done there.
I have some bad feeling about 1 as this would break encapsulation. I don't want people to specify all indirect deps there. On the other hand, we can change the behaviour in a way that the entry will be used on a match with any (!) of all (!) dependencies (currently it is used on a match with direct dependencies only). I see the value (not to mention max strategy as you pointed out) but this is quite a messy logic to be honest. If done, this needs to be very well documented.
What is your question?
Example
Context:
pkg.a
depends onpkg.b
but not onpkg.c
.pkg.c
is not defined on DESCRIPTION file ofpkg.a
pkg.c
is only released on GitHub / R-UniverseFor an actual case,
pkg.a is teal.modules.clinical
,pkg.b is teal.slice
andpkg.c is teal.data
Outcome
pkg.c
Solutions
Config/Needs/verdepcheck
ofpkg.a
to serve as hint on where to findpkg.c
Depends/Imports/Suggests
Remotes
section to insightsengineering packagespkg.c
is released on CRANteal.data
should be released in next few monthsCode of Conduct
Contribution Guidelines