> > Q1: Can I put macOS specific files there? > Yes, either there, or create a platform/macosx directory. I can make strong > arguments either way, but keeping an existing directory probably makes the > most sense. There are no other places where we've created subdirectories > specifically for macosx. It probably makes sense to consider it a sub-type of > a unix OS.
I removed macosx and created macos instead, since 2016 macOS is what Apple call its baby. > > For Windows, all files related to the installer are put in > platform/windows/install. It might be a good idea to use > platform/unix/macos/install > Check > Q2: Shall I delete those files that are no longer used? or create a > subdirectory /obsolete? > > svn maintains information for all file deletions, so there's no need to keep > old files around. If needed, they can be recovered at any time. Keeping them > in the tree just adds noise to the process. Go ahead and delete them. Check <snip> Regarding the icon Rony provided us with the provenance. I have reverted to use the official Unix png file for now but I prefer the newer one, it looks more appealing because it scales better on modern screens than a 64X64 pixel file. > > I have looked in the SVN tree and in oorexxSVN/platform/unix there is a low > resolution file oorexx.png (48X48 px) used for Unix/Linux RPM and DEB builds. > This png is also referred to in CMakelists.txt in the (obsolete) Cpack > section #Apple macOS. > > Q4: Should this section be emptied? Or can someone clean it up? Who? > Yes, remove anything that no longer applies. As I stated earlier, svn never > forgets so those sections can be recovered if they are needed. > Check > > Q5: Should I include the "Package description" from this section of > CMakelists.txt in the Readme files for the installer? > It would be a good idea, if it makes sense. I just checked, and the Windows > installer does not include this. Not sure if it is part of the other unix > installer packages or not. Check > > > Q6: Shall I include the Copyright Notice in the readme files? > > Yes. A copyright really should be in any plain text files. Check > > Q7: Is the contact mail sahana...@users.sf.net > <mailto:sahana...@users.sf.net> for macOS still correct? > > Probably not. It would be better if a contact email were a project-specific > one (perhaps one of the mailing lists) rather than a specific individual. I have refrained from inserting any Email in the installer, if Jon did not receive any mails in the last years, I think we can be sure anyone interested will come forward in other ways. > > Any other things that need consideration? > > > Does the installer you build also pick up things like release number, etc. > from CMake? You might want to take a look at > platform/windows/install/cpack.nsi.template.in > <http://cpack.nsi.template.in/> to see the types of information the Windows > installer pulls in from CMake. Any variable in that file that starts with '@" > is information that is pulled in from cmake.txt file. > I take the version number from SVN itself so it should give the same result. Here the log ++ svn info --show-item revision ../oorexxSVN + svn_revision=12149 ++ date +%Y-%m-%d + current_date=2021-02-08 + cp dmgInstaller/ooRexx5.dmg dmgInstaller/ooRexx5.0.0-12149-2021-02-08.dmg + rm -f dmgInstaller/ooRexx5.dmg A related last question Q8: Should there be an indication that this is a 64 bit build? (For macOS there is no 32 builds no more possible so it is implicit) > Rick > > > Hälsningar/Regards/Grüsse, > P.O. Jonsson > oor...@jonases.se <mailto:oor...@jonases.se> > > > > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net <mailto:Oorexx-devel@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > <https://lists.sourceforge.net/lists/listinfo/oorexx-devel> > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel