@ferventcoder okay, so basically the NuGet ecosystem does not provide the packages that we would require yet... not sure we have the manpower to conjure those packages into existence.

Correct. Right now, I'm not sure if the ecosystem is at that level, yet.

Again... I was looking for a way to reduce the maintenance burden, not to increase it 😄

:) One thing to consider is that mingw-get will likely become part of what chocolatey can intuitively install from as well. All of the alternative sources (cygwin, python, gems, etc) will likely get better in the next incarnation of Chocolatey (which I'm just about to add back in the alternative sources for) so that they do a better job of installing the alternative pkg mgr, then installing packages from (which is currently user driven, not specified from packages themselves).

Then we'll likely enhance the nuspec that describes the package and the dependencies to allow for taking dependencies on these alternative sources, thus

 <dependencies>
  <dependency id="bash" source="mingw" />
  <depencency id="less" source="cygwin" />
</dependencies>

Describe the package management #15

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions