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

Make the package noarch for Linux and Mac #191

Merged
merged 8 commits into from
Oct 24, 2024

Conversation

ccordoba12
Copy link
Contributor

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

@ccordoba12
Copy link
Contributor Author

@conda-forge-admin, please rerender

Copy link
Contributor

github-actions bot commented Sep 29, 2024

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 (recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipe/meta.yaml:

  • noarch packages can't have selectors. If the selectors are necessary, please remove noarch: python.

entry_points:
- spyder = spyder.app.start:main
osx_is_app: true
# https://github.com/conda/conda-build/issues/5385
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wow i forgot about this. glad i opened an issue for it......

@hmaarrfk
Copy link
Contributor

I guess you need to weigh the reduction in the jobs against the added complexity and linter failures....

@ccordoba12
Copy link
Contributor Author

I guess you need to weigh the reduction in the jobs against the added complexity and linter failures....

I'm fine with the complexity (I don't think it makes things too different from what we have right now). But I was about to ask you if there's something we can do about the linter, i.e. is there something like # noqa to disable this specific warning?

@hmaarrfk
Copy link
Contributor

i'm not too sure.

I'm half thinking if there is a way to maybe fix the offending character in the ico file...

@hmaarrfk
Copy link
Contributor

@conda-forge-admin please rerender

@hmaarrfk
Copy link
Contributor

well 1/2 of the linter warnings gone ....

@ccordoba12 ccordoba12 marked this pull request as draft September 29, 2024 18:02
@hmaarrfk
Copy link
Contributor

hmm, seems like this is a real problem: #192 (comment)

@ccordoba12
Copy link
Contributor Author

So, is the linter failure a bug in conda-smithy?

@hmaarrfk
Copy link
Contributor

hmaarrfk commented Oct 1, 2024

No. It’s actually indicating that the new dependency necessitates an arch dependent package.

@ccordoba12
Copy link
Contributor Author

Ok, I see. The problem is fcitx-qt5, which was added to help people from East Asian countries to type characters for their languages in Spyder.

A couple of additional questions for you:

  • If we change the selector to linux to make the package noarch, then it won't be possible to install Spyder in aarch64, right?
  • If that's the case, could you give us a hand to compile fcitx-qt5 for that architecture? I know it's too much to ask, but we're really swamped with other things.

@hmaarrfk
Copy link
Contributor

hmaarrfk commented Oct 1, 2024

So i'm helping with PRs, but.....
Do you really want to have a hard dependency on a 2 year old package?

@hmaarrfk
Copy link
Contributor

hmaarrfk commented Oct 1, 2024

@conda-forge-admin
Copy link
Contributor

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 (recipe/meta.yaml) and found it was in an excellent condition.

@hmaarrfk
Copy link
Contributor

hmaarrfk commented Oct 2, 2024

Ok with conda-forge/fcitx-qt5-feedstock#5 merged soon you should be good to go.

@ccordoba12
Copy link
Contributor Author

ccordoba12 commented Oct 2, 2024

Ok with conda-forge/fcitx-qt5-feedstock#5 merged soon you should be good to go.

That's awesome! Thanks @hmaarrfk!

Do you really want to have a hard dependency on a 2 year old package?

We received several requests about that. And I don't know about other Qt packages that provide input facilities on Linux for East Asian languages. So, I prefer to deal with that inconvenience rather than not giving those users a better out of the box experience when working with Spyder.

@hmaarrfk
Copy link
Contributor

hmaarrfk commented Oct 2, 2024

understood!

@hmaarrfk
Copy link
Contributor

hmaarrfk commented Oct 2, 2024

And I don't know about other Qt packages that provide input facilities on Linux for East Asian languages.

I always thought that this was Gnome's job, to provide some input language and that the editors were just receiving some unicode codepoint to display...

@ccordoba12
Copy link
Contributor Author

I always thought that this was Gnome's job, to provide some input language and that the editors were just receiving some unicode codepoint to display...

I think the problem is Conda envs are like chroots (not exactly virtual machines but like a Linux system within the host one). Since they come with their own set of Xorg/Qt/Gtk packages, they can't use the facilities provided by the host system.

@hmaarrfk
Copy link
Contributor

hmaarrfk commented Oct 2, 2024

Xorg/Qt/Gtk packages, they can't use the facilities provided by the host system.

this sounds like a real conda-forge problem. I don't know anybody that uses Pinyin type inputs on Ubuntu and I've never used it myself so I can't really test....

@ccordoba12
Copy link
Contributor Author

this sounds like a real conda-forge problem.

I think so too, in the sense that conda-forge on Linux is close to be the conda-forge Linux distro. But since many people wanted things to work out of the box in conda-forge envs (i.e. without worrying about what system packages they had to to install), it was inevitable.

@ccordoba12 ccordoba12 marked this pull request as ready for review October 22, 2024 15:46
conda-forge.yml Outdated
noarch_platforms:
- linux_64
- osx_64
- win_64
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hmaarrfk, do we need win_64 here or can we remove it for now?

Other than that, this should be ready to go, right?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think we need it, otherwise it won't trick conda-smithy to generate the windows builds. maybe. i'm not sure, try without it?

That's because we're only building a noarch version for Mac and Linux
@ccordoba12
Copy link
Contributor Author

@conda-forge-admin, please rerender

@ccordoba12
Copy link
Contributor Author

Ok, I think this one is ready. Thanks @hmaarrfk for all your help with it!

@ccordoba12 ccordoba12 merged commit 8533ef9 into conda-forge:main Oct 24, 2024
9 checks passed
@ccordoba12 ccordoba12 deleted the make-package-norach branch October 24, 2024 16:51
@hmaarrfk
Copy link
Contributor

Great. Hopefully this helps more than it causes churn

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

Successfully merging this pull request may close these issues.

3 participants