@buhtz wrote her: https://github.com/bit-team/backintime/issues/1401#issuecomment-1413244974
We do have a changelog. IMHO no need for redundancy. A good/motivated distro maintainer take care of such a file.
Yes, our changelog would work (if I hadn't forgotten to capture the newly discovered dependencies there BEFORE the release :-( BTW: There is still open work for me to document the weak dependencies (mainly on required cmd line tools)...
if the repo is setup correctly fitting to the python packaging standards (e.g. using a pyproject.toml) all dependencies are "coded" in there.
That sounds very promissing, I have never tried this before! I think we need to get a clear picture if and how pyproject.toml - maintains python-external dependencies (like eg. themes and icons or required cmd line tools like rsync) in a distro-independent (!) way (different pkg names), e.g.: Ubuntu: oxygen-icon-theme Arch: oxygen-icons If the answer above question is YES: Could we end up then in doing the pkg maintenance half-way ourselves then (instead of letting downstreams do the work)? Also: My current understanding is (by flying over the PEP-specs for this) that pyproject.TOML is mainly meant for metadata and *build* dependencies while I have not directly seen a way to separately specify the *installation* dependencies (but I have not fully read the PEP-specs so far). On Thu, 2023-02-02 at 01:04 +0100, BiT dev wrote:
As lesson learned from our current rollout of v1.3.3 I suggest to maintain a separate
"Package Maintainer NEWS" file which shall contain pkg maintainer relevant changes like
- changed dependencies - installation path changes - unexpected file and folder renamings etc.
Any opinions (also on the best file name for this)?
Optionally we could maintain a list of known BiT packages incl. a link to the pkg maintainer web sites in our wiki or FAQ to direct users with packaging-related issues to the according responsible pkg. maintainer.
I have asked for community support to compile such a list in one of our issues:
https://github.com/bit-team/backintime/issues/1401#issuecomment-1412915694
_______________________________________________ Bit-dev mailing list -- bit-dev@python.org To unsubscribe send an email to bit-dev-leave@python.org https://mail.python.org/mailman3/lists/bit-dev.python.org/ Member address: python@altfeld-im.de