| Re: [hatari-devel] Preparing release 2.3 |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
Hi,
On 10/15/20 11:48 AM, Nicolas Pomarède wrote:
Mostly some reports about python UI. You can backport those patches into
hatari if you think they're relevant, or contact the patches' author
to discuss them.
Except for the still open "python3" hashbang
issue, I've applied what I thought relevant,
and pushed them.
I also did major update to release checklist
(=what we should ideally do before release).
What you think, how does the new one look like:
https://git.tuxfamily.org/hatari/hatari.git/plain/doc/release-checklist.txt
?
Some automation for build testing different Hatari
configurations, and running "make test" with them
would be nice eventually.
Thomas, didn't you do something already for that
in your GitHub repo? If yes, please add link to
release checklist.
So, I don't see any real packaging issues that we should take care of,
which is good news.
Looking at OpenSUSE, it seems that Hatari has been
discontinued from it, but there are community
builds:
https://build.opensuse.org/search?search_text=hatari
Latest one seems to support building package for
most of the distros without modifying Hatari:
https://build.opensuse.org/package/show/home:Chrischaan/hatari-20201009
Another user applied patch to support
re-producible builds:
https://build.opensuse.org/package/view_file/home:kahu2000/Hatari/0001-no-time-date.patch
=> I think we should actually get rid of *_fileid stuff in the sources
before release.
They're obsolete with GCC adding build IDs to
object files, and distros requiring reproducible
builds. I've never heard anybody needing them...
Is there any objection on me removing them?
- Eero
PS. I'm still running / checking TOS boot tests.
I may be away for weekend, which would mean
the compatibility list update going to the next
week...