Aug 20, 2023 08:24:47 Steve A <stevena...@gmail.com>: > Hi Nicolas, > Thanks for your attention re packaging Scid vs PC. ;> > > Unfortunately we do have some world writeable files and directories. > But briefly, you can/are welcome to chmod all to 664 and ship the package. > This will only make minor obscure-feature failures when run by users not in > the group of the user which installed it. Changing all the 666 to 664 in the > makefile would be a reasonable/maybe sufficient step. > If individuals send you bug reports regarding permissions, i will handle them. > > In a bit more detail - the features which may fail or not work 100% *when run > by users not in the group* are the mate-in-N puzzles and book tuning. And > *possibly* the old and little used engine phalanx and Play Tacgame. > > The problem is due to the number of features of the project, and these small > features never being made truly mutil-user friendly due to the testing > obligations and the fact most linux hobbyists systems are hardly multiuser > anyway. > > I must add i'm not terribly authoritive about all this, and some others may > be able to add more. > regards, Steven > > On Sun, Aug 20, 2023 at 3:47 AM Nicolas Formichella <stig...@outlook.fr> > wrote: >> Hello, >> >> To introduce myself, I am a hobbyist Linux packager, especially for SUSE's >> openSUSE Tumbleweed[1][2] >> >> As such, I like to package as much software as possible to enrich the >> distribution, and so scid_vs_pc comes in >> >> I made a first package draft, but had some questions before I can continue >> the process of packaging >> >> — openSUSE has a strict security policy[2], and scid_vs_pc breaks it by >> having a lot of world-writeable files included >> ($SHAREDIR/bases/;$SHAREDIR/books;$SHAREDIR/engines/phalanx/eco.phalanx) >> >> I would like to know if those definitely need to be shipped as >> world-writeable, or if they can be switched to 664? >> >> Thanks in advance, >> Nicolas FORMICHELLA >> >> [1]: https://opensuse.org >> [2]: https://en.opensuse.org/openSUSE:Package_security_guidelines#audit_bugs >> >> _______________________________________________ >> Scidvspc-users mailing list >> Scidvspc-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/scidvspc-users Hello Steven,
Thank you so much for your answer, this is now implemented, and I'll make sure to forward you any report - I would like to report that `ScidvsMac-HowTo.rtfd.tgz` in `doc/` is in the 4.24 archive with an executable bit set. Since it triggers a packaging error, I removed it from my package. Would it be possible to strip it from the archive too, as it is fully unnecessary? - Does `README.bitmaps` need to be in both `bitmaps` and `bitmaps2` or a symlink would be sufficient (It fails my package due to the fact that they are the same file) Regards, Nicolas FORMICHELLA _______________________________________________ Scidvspc-users mailing list Scidvspc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scidvspc-users
