-
-
Notifications
You must be signed in to change notification settings - Fork 5k
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.
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
Added recipe for htop #1598
Added recipe for htop #1598
Conversation
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/htop:
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Seems like a nice recipe to have. What is the reason for closing? Please let us know if there is anything we can do. Normally I use |
Ow! Closing the PR was non intended. Nonetheless, my local test (a simple |
Ok, cool. Just wanted to make sure you hadn't lost hope. 😄 Hmm...so Could you please provide info about your system? Guessing Linux of some kind? |
Yep, that seems right. Could you please submit a PR to the feedstock? |
|
||
source: | ||
git_url: https://github.com/hishamhm/htop.git | ||
git_rev: {{ version }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we please switch this to a tarball instead?
fn: {{ name }}-{{ version }}.tar.gz
url: https://github.com/hishamhm/htop/archive/{{ version }}.tar.gz
sha256: <some checksum>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
requirements: | ||
build: | ||
- automake | ||
- gcc |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please drop gcc
as we already include the compilers on the VMs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
skip: true # [win] | ||
|
||
requirements: | ||
build: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add toolchain
to properly configure the VM compilers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
- automake | ||
- gcc | ||
- libtool | ||
- ncurses |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please pin to 5.9*
to match our global pinnings.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also shouldn't this be a run time dependency too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- I'm not sure if I pinned it right...
- Now added to run time dependency
|
||
about: | ||
home: https://github.com/hishamhm/htop/ | ||
license: GNU General Public License, version 2 (GPL-2.0) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please shorten to GPL-2
or similar.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also please include the license file by adding license_file: COPYING
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
|
||
extra: | ||
recipe-maintainers: | ||
- keuv-grvl |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Please add terminal newline.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
build: | ||
- automake | ||
- gcc | ||
- libtool |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add pkg-config
? Seems like we can't find the headers for ncurses
. So this may help.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It did not change anything on my system, so I did not add it. But let met know if I have to.
set -euo pipefail | ||
./autogen.sh | ||
./configure --prefix=$PREFIX | ||
make |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a make check
that we can run?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is one, but it does not seem to check something. I added it anyway.
- automake | ||
- gcc | ||
- libtool | ||
- ncurses |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also shouldn't this be a run time dependency too?
@@ -0,0 +1,6 @@ | |||
#!/bin/bash | |||
set -euo pipefail |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add the following to fix the include failure.
export CFLAGS="-I${PREFIX}/include ${CFLAGS}"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Given the changes mentioned above and your PR ( conda-forge/ncurses-feedstock#23 ), I was able to build |
Hi! This is the friendly automated conda-forge-linting service. I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug. |
Thank your @jakirkham for your review! I added your suggestions to the current PR, and it works on my machine using: conda build recipes/htop
conda search htop --use-local
conda install htop --use-local Let me know if you can reproduce it. The odd thing is: I dropped
So I guess |
@@ -0,0 +1,355 @@ | |||
GNU GENERAL PUBLIC LICENSE |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We shouldn't need this right? We are just grabbing it from the source code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So which license file should I add?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We shouldn't need to add one.
The feedstock will get a BSD 3-Clause license as it is the standard.
Adding the license_file
portion in the recipe was the only thing we needed to do. However, it pulls the license file from the htop
's source. So it isn't using this file either.
- toolchain | ||
- automake | ||
- libtool | ||
- ncurses >=5.9 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be ncurses 5.9*
. Otherwise this will break when ncurses 6.0
is released here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
- ncurses >=5.9 | ||
|
||
run: | ||
- ncurses >=5.9 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as above.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
To build, we normally use a Docker container. This should be easy to do locally as long as you have Docker installed. To get the build artifacts out, you may need to use PR ( #1508 ). This will drop the package in |
So I built this fine in the Docker container and was able to use it successfully in our container and Continuum's. Not sure what is causing you build issues locally, but would recommend using our Docker container and seeing if the resulting package will work on your OS. |
I successfully built Everything seems to work fine :) So is conda-forge/ncurses-feedstock#23 still relevant? |
Great! Glad this works for you. 😄 We can take a closer look at the build issues you encountered outside the Docker image in an issue at the feedstock. Just make sure to ping me as I'm often unsubscribed from feedstocks to keep notifications manageable.
No, it sounds like it isn't. Would you mind closing it and making a note about this? |
Could you please revert/remove commit ( c3ef0b8 ) from the PR? Edit: Also please drop the license file. |
This reverts commit c3ef0b8.
Thanks @keuv-grvl. |
Soon you should get an email that invite you to join conda-forge, @keuv-grvl. Once accepted you will be added to a team with the same name as this recipe. Those will give you permissions on the feedstock (repo) for this recipe. Make sure when proposing any change that you go through the typical GitHub workflow of forking the feedstock and making changes in your fork that you PR back. Once merged CIs will build and deploy any changes you make. Please let us know if you have any questions and welcome to conda-forge. 😄 |
|
No description provided.