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

Support file system sources. #119

Closed
RichiCoder1 opened this issue Feb 24, 2014 · 6 comments
Closed

Support file system sources. #119

RichiCoder1 opened this issue Feb 24, 2014 · 6 comments
Assignees
@RichiCoder1
Labels
Feature Issues that introduce new functionality to the project, instead of updating existing functionality
Milestone
0.15.0

Comments

@RichiCoder1
Copy link
Contributor

I still need to figure out the best way to support file system sources.
@RichiCoder1 RichiCoder1 added this to the 0.13 milestone Feb 24, 2014
@gep13
Copy link
Member

gep13 commented Feb 24, 2014

Chocolatey already handles this:

https://github.com/chocolatey/chocolatey/wiki/CommandsSources

Is there something else that we need to do here?

@RichiCoder1
Copy link
Contributor Author

Chocolatey does support it, but currently pulling from a file system will basically break both the remote and package views.

@gep13
Copy link
Member

gep13 commented Feb 24, 2014

ah, gotcha.

@gep13 gep13 removed the TaskItem Non-bug, non-feature related things. Could be refactoring. Sometimes non-code related things. label Sep 16, 2014
@RichiCoder1 RichiCoder1 added Feature Issues that introduce new functionality to the project, instead of updating existing functionality Tests Issues related to the tests (NUnit, xUnit, Pester, Etc) and removed Bug Issues where something has happened which was not expected or intended Feature Issues that introduce new functionality to the project, instead of updating existing functionality labels Sep 22, 2014
@gep13 gep13 removed the 0 - Backlog label Feb 10, 2015
@gep13 gep13 modified the milestones: 0.14, 0.13 Mar 21, 2015
@RichiCoder1
Copy link
Contributor Author

Related to #267.
We should be using the Chocolatey to both retrieve sources and interrogate them.

@RichiCoder1 RichiCoder1 self-assigned this Jun 2, 2016
@RichiCoder1
Copy link
Contributor Author

I think this technically works. Need to investigate...

@RichiCoder1 RichiCoder1 added Feature Issues that introduce new functionality to the project, instead of updating existing functionality and removed :Chocolatey Tests Issues related to the tests (NUnit, xUnit, Pester, Etc) labels Feb 14, 2017
@RichiCoder1
Copy link
Contributor Author

Pretty sure this works now, and you can now manage sources through GUI itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@RichiCoder1 RichiCoder1

Labels
Feature Issues that introduce new functionality to the project, instead of updating existing functionality
Projects
None yet
Milestone
0.15.0
Development

No branches or pull requests
2 participants
@gep13 @RichiCoder1