Hi Les,
On 2021-01-09 21:00, Les Mikesell 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 personally agree to the approach of adding packaging scripts/metadata
to upstream.
However, at least the Debian project seems to have a strong opinion on
how this should be done,
see https://wiki.debian.org/UpstreamGuide#Pristine_Upstream_Source :
Some projects include a rough /debian directory among source files
to
[...]
While this is a good effort, it is better to leave it out of the
final
tarball as it can interfere with debian's own packaging effort.
[...]
Keeping it only in your VCS repository is usually a much saner
default
if it lives in a specific packaging branch, which mimics what Debian
package maintainers do using git-buildpackage.
[...]
I suppose other distros have their own opinions as well.
As an upstream author, I would not know how to handle all these distro
specifics...
Raoul
--
DI (FH) Raoul Bhatia MSc
E-Mail. ra...@bhatia.at
Tel. +43 699 10132530
_______________________________________________
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/
