On Tue, Feb 04, 2025 at 05:35:29AM +0000, Julian Gilbey wrote: > And I thought some more about this... > [...] > > source: python-glue-core > binary: python3-glue-core > breaks/replaces: python3-glue (and possibly also glueviz (<< ...), > depending on where the support files end up)
Hmm, as the package is called "glue_core" but it provides a module called "glue" (as in: "import glue"; I wish packages wouldn't do this!), perhaps it would be better to keep the current name and have: source: python-glue-core or python-glue (not sure which is better) binary: python3-glue provides: python3-glue-core breaks/replaces: possibly glueviz (<< ...), depending on where the support files end up) > source: python-glue-gt > binary: python3-glue-gt > provides: glueviz > breaks/replaces: glueviz (<< ...) And for this one, we could keep the same source name as at present, to make less work for everyone: source: glueviz binary: glueviz provides: python3-glue-gt and then later, if wanted, there's the possibility of a jupyter-based package; if it turns out that it provides the command "jupyter glue" (I haven't checked), then calling the package "jupyter-glue" with a virtual name of "glueviz-jupyter" or vice versa might make sense. On salsa, we could rename the glueviz.git repository as python-glue.git or python-glue-core.git and create a fresh glueviz.git repository for the glue-gt frontend; it might otherwise be confusing. An alternative is to keep glueviz.git for the glue-core Python package and create a new repo called glue-gt.git or glueviz-gt.git for the frontend. Best wishes, Julian
