wxRemind is a front/back-end to remind, which is used for keeping track of appointments and tasks. Reproducible: Always
Created attachment 141024 [details] ebuild for version 41 Here is an ebuild for version 41. Note that this uses the 'src' packages. The developer provided the following notes from the Python cookbook on construction of the executables': [Python Cookbook (2nd ed) recipe 16.12]: "Binding Main Script and Modules into One Executable on Unix". The idea is to create a header script file, a zip file containing the *.py for the required modules and then 'cat' the header and zip files to produce a single, executable file. This is what the ebuild does with the 'src' package. That is, the wxremind executable is a zip file with a script header attached. As such the ebuild makes some direct calls to 'zip', which may not be wanted in an ebuild. Given the above description of creating the executables, I'd like to know if there is any harm in just using the 'binary' package. I'm also unsure about what to do with documentation. There is none in the src package. An email might need to be sent to the developer to ask their opinion. I'm not sure if any other distros package wxremind which we can compare with.
Created attachment 141122 [details] ebuild for version 44 ebuild for version 44, that contains some slight 'improvements' over the previous one, namely installing a .desktop file for the wxremind program. Using an icon from gnome-icon-theme for this desktop entry, so added as a dependency.
Created attachment 144492 [details] ebuild for wxremind v79
Created attachment 160041 [details] ebuild for version 88
Created attachment 160043 [details] docs package needed by ebuild for version 88 This package should go into FILESDIR. Apologies, I know that isn't correct, but I don't have a file server so it is easier for me to place this file in FILESDIR and check it into my overlay.