Repository navigation
Conversation
|
Do we really want that? Is it needed? |
|
(I mean probably want that - but what are we breaking currrently?) |
|
I guess it's more of a completeness thing than anything else. it declutters the output, and makes the dependency list that is generated by paket the same as nuget. in a project of any size, (and I have a few at work), the depency list is relatively large. a good chunk of these dependencies are transitive. it leads to larger lock files I guess, and I need to justify the difference to the people I work under ;-) |
|
ok will look into it |
|
all looks good. just ran master against my solution here, and it worked as expected. |
|
Do we influence the packaged dlls with it? I mean for packages that don't use dependencies but bundle their stuff we still need to package all deps. Otherwise that would create a bug right? |
|
that code just has an impact on the dependencies list, not on the packaged dlls |
brings the dependency list in line with exactly what nuget produces (as far as I can tell).