On Sat, Jan 9, 2021 at 2:01 PM Les Mikesell <lesmikes...@gmail.com> wrote:
> On Sat, Jan 9, 2021 at 1:39 PM Raoul Bhatia <ra...@bhatia.at> wrote: > > > >> I understand that packages can also be done badly, but if I do not trust > > pre-packaged software, there are normally easy ways to package myself. > > > > Anybody care to share their perspective? > > "Well maintained" packages are always great, but they can leave you > stranded if you need some quick fix and there is some problem with the > maintainer or getting the repository updated. In my opinion, the > 'best of all worlds' is where the source package includes the > packaging script so you don't really need to know anything to build > your own package if that is ever necessary. > I think it really depends on what you're packaging. Some packages are quite simple and upstream could account for most of the packaging guidelines, but keep in mind, even among distros that use the same packaging (RPM or DEB, etc) that the packaging guidelines can vary significantly. Also, in the specific case of BackupPC there are a lot of things that need to be taken care of. If you take a look at the source files[1] used to package BPC on Fedora/EPEL you'll see things like: 1. The Spec file of course, and it takes care of a bunch of things including setting proper SELinux contexts. 2. Apache htaccess file so apache is ready "out of the box" 3. Logrotate config 4. tmpfile config 5. C wrapper so BackupPC_Admin which is perl based can run setuid/setgid. 6. SystemD service file I don't think it's practical for upstream to manage all of this across all distros. Some will be similar, others may be very different. Thanks, Richard [1] https://src.fedoraproject.org/rpms/BackupPC/tree/master
_______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/
