<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi guys,<br>
<br>
Well...<br>
<br>
When I finally got a breather, I managed to look into this libs3
thing.<br>
</p>
<p><a class="moz-txt-link-freetext" href="https://salsa.debian.org/bacula-team/bacula-libs3/-/commit/451cd1223bf22f72761330b22c72a6e7e2db0b7f">https://salsa.debian.org/bacula-team/bacula-libs3/-/commit/451cd1223bf22f72761330b22c72a6e7e2db0b7f</a></p>
<p>This will build packages with /usr/lib/bacula as location.<br>
The whole Makefile is a bit cowboy style and the process doesn't
follow Debian packaging as it should (control file is a weird,
rules file doesn't exist...)<br>
<br>
I can only presume the idea is to take this upstream src and, at
the end, make it part of something more meaningful, but you know
what they say about presumptions.<br>
<br>
With that in mind, I didn't want to spend time polishing it for
now. <br>
I just located where the bodies are buried and managed to do some
changes and not to cause pkgs content overlapping.<br>
<br>
<br>
How do we proceed from here? What is a general idea how this libs3
should be:<br>
- named<br>
- installed to proper location X (is /usr/lib/bacula ok? what
about the other files in those packages?)<br>
- actually packaged (a proper debian/control and other files
should be written based on upstream source, instead of running
"make deb" within upstream src).<br>
<br>
So... How do we proceed?<br>
<br>
Thnx!<br>
<br>
Best regards,<br>
</p>
<div class="moz-signature">-- <br>
<b>Mario</b><br>
<br>
</div>
</body>
</html>