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

Klayout should only build release versions only not main #290

Open
atorkmabrains opened this issue Feb 10, 2023 · 2 comments
Open

Klayout should only build release versions only not main #290

atorkmabrains opened this issue Feb 10, 2023 · 2 comments

Comments

@atorkmabrains
Copy link

atorkmabrains commented Feb 10, 2023

@proppy It's preferred to use the release versions only of klayout for builds and not to build the main branch:

https://github.com/KLayout/klayout/tags

@proppy
Copy link
Contributor

proppy commented Feb 10, 2023

@atorkmabrains for conda-eda we usually want to be able track, build and package the latest version of tools (even if they have not yet released a formal version).

#193 has some discussions about using conda-forge instead for more "stable" released version of the tools.

but we could also have stable version also packaged in conda-eda (they should conflict because the version/git hash will be different).

maybe @mithro @PiotrZierhoffer @ajelinski have some thoughs around this?

@atorkmabrains
Copy link
Author

Having a "stable" branch of the conda environment would be really helpful.

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

No branches or pull requests

2 participants