Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Packages with content folders cannot have a dependency without also having a content folder #290

Closed
ferventcoder opened this issue May 22, 2015 · 0 comments
Closed

Packages with content folders cannot have a dependency without also having a content folder #290

ferventcoder opened this issue May 22, 2015 · 0 comments
Assignees
@ferventcoder
Labels
5 - Released Bug Priority_LOW
Milestone
0.9.9.7

Comments

@ferventcoder
Copy link
Member

If you ever run into this old gem - "External packages cannot depend on packages that target projects"

This is a nuget packaging bug. I call it a bug, I'm sure some folks would call it a feature.

References:
@ferventcoder ferventcoder added this to the 0.9.9.7 milestone Jun 12, 2015
@ferventcoder ferventcoder self-assigned this Jun 12, 2015
ferventcoder added a commit that referenced this issue Jun 12, 2015
@ferventcoder
(GH-205)(GH-194)(GH-290) Vendor NuGet.Core
80160ae 
Vendoring NuGet.Core allows us to take advantage of our own fixes to
the provider. There are things that have been wanted for awhile that
don't have a workaround to change the setting.

- GH-290 - packages no longer have a restriction on content folders
that produces the "External packages cannot depend on packages that
target projects". I'd like to call it a bug, and for Chocolatey it
certainly is.
- GH-194 - Fix minimum NuGet client version reports Chocolatey version
instead of NuGet's version, which is fine for packages on Chocolatey,
but the ones on NuGet usually have this filled in, which makes them
impossible to install with choco.
- GH-205 - Enhance the nuspec - first wave. Add the most oftenly
requested url for the nuspec, the packageSourceUrl and several other
urls plus add in replaces, provides and conflicts as placeholders for
now.
ferventcoder added a commit that referenced this issue Jun 12, 2015
@ferventcoder
Merge branch 'stable'
72cf0d8 
* stable:
  (GH-205) Enhance the nuspec template
  (GH-205)(GH-194)(GH-290) Vendor NuGet.Core
ferventcoder referenced this issue in chocolatey/nuget-chocolatey Jun 12, 2015
@ferventcoder
Remove the content folder restriction
5f5fd2d 
When using the core, this bug is killer and doesn't mean anything once
you get outside of NuGet.
@jpluimers jpluimers mentioned this issue Jul 21, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ferventcoder ferventcoder

Labels
5 - Released Bug Priority_LOW
Projects
None yet
Milestone
0.9.9.7
Development

No branches or pull requests
2 participants
@ferventcoder @gep13