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

List dependencies outside pip #34

Closed
chriscabral opened this issue Oct 16, 2013 · 5 comments
Closed

List dependencies outside pip #34

chriscabral opened this issue Oct 16, 2013 · 5 comments

Comments

@chriscabral
Copy link

I had to install memcached before I could install the requirements. I know this is a pip dependency problem but just thought you might want to list the external dependencies on the readme.
@pydanny
Copy link
Member

pydanny commented Oct 16, 2013

Good point! Thanks!

@pydanny
Copy link
Member

pydanny commented Nov 12, 2013

Was this caused when trying to install the base requirements.txt file or when trying to install requirements/local.txt?

@keybits keybits mentioned this issue Jan 29, 2014
Merged
theskumar pushed a commit to theskumar-archive/cookiecutter-django that referenced this issue Feb 13, 2014
@theskumar
Add documentation on 'getting up and running'
d615446 
Some hopefully usefully instructions to help people get up and running.

Re: Issue cookiecutter#34 On my machine I didn't need to install memcached to successfully install the local requirements.

Re: Issue cookiecutter#39 I've linked to this issue for now. It would be good to remove the need for those steps and then this link can be removed.
@luzfcb
Copy link
Collaborator

luzfcb commented Dec 5, 2014

@pydanny What do you think of listing the external dependencies (non-python dependencies) in a file named "requirements.apt"

eg.:
https://github.com/luzfcb/sisposto/blob/master/requirements.apt

Ok. The first problem with this approach is that my "requirements.apt" file is specific to Ubuntu packages.

Second problem is that the package names may be slightly different between Linux distributions.

However, I believe, that can at least be a guide on which native libraries must be installed so that the dependencies python has successful installation. Is less tedious than going all documentation of all dependencies, and find out which native library is missing (often this is not explicit in the documentation).

@pydanny
Copy link
Member

pydanny commented Dec 7, 2014

Hey @luzfcb , I saw your google chat message but couldn't respond at the time.

I like the idea of adding a requirements.apt file. Make it for Ubuntu packages, just place comments in the file that it is designed for that particular Linux flavor. That way it serves as you suggested, a guide for all linux users.

luzfcb referenced this issue in luzfcb/cookiecutter-django Mar 14, 2015
@luzfcb
add requirements file of external dependencies (non-python dependenci…
1ceae50 
…es), named "requirements.apt" - fix issue #34
luzfcb added a commit that referenced this issue Apr 13, 2015
@luzfcb
Merge pull request #200 from luzfcb/issue-34
6626c92 
add requirements file of non-python dependencies and helper scripts - fix issue #34
@theskumar
Copy link
Contributor

Seems like has already been resolved. @luzfcb can you please confirm and close this issue if it's not needed anymore.

@pydanny pydanny closed this as completed Aug 9, 2015
@luzfcb luzfcb mentioned this issue Oct 20, 2015
Merged
@luzfcb luzfcb mentioned this issue Jun 8, 2016
Closed
@luzfcb luzfcb mentioned this issue Aug 15, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@pydanny @theskumar @luzfcb @chriscabral