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

Path to using package.yml for remaining (no flatpak available) 3rd party packages? #67

Open
ermo opened this issue Jun 18, 2024 · 0 comments
Labels
enhancement New feature or request help wanted Extra attention is needed
Milestone

Comments

@ermo
Copy link
Contributor

ermo commented Jun 18, 2024

Ikey Doherty
Btw the current third party, is a deprecation window scheduled...?
Or could we do an absolute cheeky and yml convert it for temporary lease of life
And then teach ypkg to add the comar .py bits into the correct part of the archive
And drop eopkg build completely
Ie if it finds comar/*.py shove them in
Add relevant pspec pieces too
alternatively do the above and hack eopkg build to call out to ypkg/solbuild and clone the repo to a staging location,
So that the existing instructions continue to work sorta
Mad adhd mental dump ^ but may give some ideas rather than continuing to give life support for the old format which I never got around to fully murdering.

@ermo ermo added enhancement New feature or request help wanted Extra attention is needed labels Jun 18, 2024
@ermo ermo added this to the Py3 port milestone Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
Status: Todo
Development

No branches or pull requests

1 participant