|
From: Christoph L. <chr...@it...> - 2018-04-02 16:33:29
|
Am 02.04.18 um 15:31 schrieb Johnny A. Solbu:
> On Monday 2. April 2018 14.39, Christoph Lechleitner wrote:
>> Am 02.04.18 um 12:41 schrieb Johnny A. Solbu:
>> Adding source repo support to the underlying software ("PBA") would require a lot of developer time
>
> We use reprepro for this «reprepro includedsc <repo name (jessie/wheezy/whatever)> package_version.dsc», and it add the source files in the proper repo all by itself.
There are 10s of solutions, we developed ours when there were maybe 2 that didn't fit our needs back then.
> And unless you are the copyright holder and publish the packages for everyone to download, you often have no choice but to provide the source packages.
> GPLv2 §3 and GPLv3 §6 states that one need to ship the source package, /or/ provide a written offer valid for 3 full years after last binary release stating that anyone asking for the source package should get it. Anything else is a violation of the GPL license[1].
Hmm. Packaging "ate" the github link in the control file, but the description points to my github fork, should be satisfactory.
The other few 3rd party projects we re-compile (for windows crossbuilding) are covered in a similar way, the (re)packaging sources are publicly available via anonymous svn.
Interesting point though.
>>> If one want to make changes or customize the deb package,
>>
>> ... then one should and would use the upstream git anyway (which is fully debianzed) or maybe use the source packages from Debian or a Debian derivate.
>
> Debian provides tools available for automatically checking for the latest version, download it, apply any patches and declare it ready for build.
What's that tool's name?
I didn't read up in this area for many years, because I didn't have to ;-)
We don't do re-packaging often, but only if we have to.
Besides version jumps beyond difficult versions in debian or centos versions used by our customers (some 5 cases) we had to apply situation-critical 3rd party patches to the debian kernel before they made it through the normal process.
> It is this process Debian packagers use for updating package sources.
> We do this on our public local repo, for our servers.
How public?
Asking for a friend ;-)
Our repos as well as our clean room builders (dedicated servers, with scripts around pbuilder) are organized in a slightly non-standard way, and I don't want to change that anytime soon (there are reasons we do it a bit differently).
This is why introduction of source repos will require more work than one might expect. It is on our wishlist though, for years, it will happen, maybe this summer.
Regards, Christoph
|
