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.

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

libudev for cos7 #41

Closed
hmaarrfk opened this issue Nov 30, 2020 · 8 comments
Closed

libudev for cos7 #41

hmaarrfk opened this issue Nov 30, 2020 · 8 comments

Comments

@hmaarrfk
Copy link
Contributor

Is there any reason why this CDT is in "custom-cdt"

name: libudev-devel-cos6-x86_64

Can we move it out of there? It is needed for libusb conda-forge/libusb-feedstock#6

@beckermr
Copy link
Member

I don't follow what the issue is.

@hmaarrfk
Copy link
Contributor Author

hmaarrfk commented Dec 1, 2020

i guess then i don't understand why libudev wasn't built for cos7. Is it incompatible?

@beckermr
Copy link
Member

beckermr commented Dec 1, 2020

I only built the CDTs needed at the time when we migrated from feedstocks to building them all in this repo. If we need more, we should add them.

@hmaarrfk
Copy link
Contributor Author

hmaarrfk commented Dec 1, 2020

great! got it.

@hmaarrfk
Copy link
Contributor Author

hmaarrfk commented Dec 1, 2020

I guess i ran into #40 when I tried to make the PR last night.

@hmaarrfk
Copy link
Contributor Author

hmaarrfk commented Dec 1, 2020

Is it as simply as copy pasting the files and adjusting them as needed?

@mbargull
Copy link
Member

libudev-devel is provided by systemd-devel in CentOS 7. You could do something like

- {{ cdt('libudev-devel') }}  # [cdt_name=='cos6']
- {{ cdt('systemd-devel') }}  # [cdt_name=='cos7']

@ryanvolz
Copy link

ryanvolz commented Feb 4, 2021

libudev-devel is provided by systemd-devel in CentOS 7. You could do something like

- {{ cdt('libudev-devel') }}  # [cdt_name=='cos6']
- {{ cdt('systemd-devel') }}  # [cdt_name=='cos7']

Using this suggestion works for libusb and I'd imagine is the way to go for any other packages that might be affected. I think this can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants