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

Move from scheme-docker complete #6

Open
lassik opened this issue Apr 14, 2020 · 6 comments
Open

Move from scheme-docker complete #6

lassik opened this issue Apr 14, 2020 · 6 comments

Comments

@lassik
Copy link
Contributor

lassik commented Apr 14, 2020

All containers under weinholt/scheme-docker are now duplicated under scheme-containers.

Many Schemes additionally have a new head tag for a container that tracks the latest developments and can be rebuilt on demand.

@weinholt
Copy link
Contributor

Excellent news. What do we need to do to maintain the containers so that they are up to date with the latest releases, did you have something planned already?

I also feel like many of the containers left under my namespace should be deprecated. Some of them haven't been used and can be removed, but a few of them can be replaced with a "FROM schemers/foo" dockerfile with automatic rebuilding enabled.

@weinholt
Copy link
Contributor

The uscan tool from Debian devscripts can monitor new software releases basically anywhere. You describe the location in a watch file and it will scan the site for version numbers.

@lassik
Copy link
Contributor Author

lassik commented Apr 14, 2020

Excellent news. What do we need to do to maintain the containers so that they are up to date with the latest releases, did you have something planned already?

Thanks! Ideally implementation-metadata would have the info, and scheme-containers would have a repo with the generator, auto-triggered whenever the metadata changes.

I don't have any auto-scouting in place yet. uscan looks like it has a lot of features and would probably be fine, or whatever tool repology.org uses (maybe they use uscan!)

I also feel like many of the containers left under my namespace should be deprecated. Some of them haven't been used and can be removed, but a few of them can be replaced with a "FROM schemers/foo" dockerfile with automatic rebuilding enabled.

Right. Feel free to change the scheme-docker repo as you see fit. I have a fork and clone of it, plus most or all of the repos under scheme-containers have kept the Git histories from the equivalent scheme-docker branches. So we should be able to salvage anything missing.

@lassik
Copy link
Contributor Author

lassik commented Apr 14, 2020

I think Repology only tracks distros though, not the upstream repos. We should track both for Scheme. Repology has a nice API that lets us easily track distros. Maybe uscan will work to handle upstreams.

@lassik
Copy link
Contributor Author

lassik commented Apr 18, 2020

@weinholt Do you have prior experience using uscan yourself?

@weinholt
Copy link
Contributor

A little bit, I need to use it for the Debian packages I maintain.

https://wiki.debian.org/debian/watch

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