News for hackers. Stuff that matters.
Re:Sequoia PGP is now LGPL 2.0 by dathinab on Monday October 18, 2021 @08:55PM (#28913740)
> available and buildable

But what does buildable mean, no-one but you has access to your CI (which also might likely not be public).

So do you need to provide another CI, a make-file you maintain additionally, etc.? Or is it good enough so that someone could run "the right CLI commands to build and link the project".

Re:Sequoia PGP is now LGPL 2.0 by anderskaseorg on Monday October 18, 2021 @11:00PM (#28914405)
You can read this in the license:

> The “Corresponding Source” for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities.

A good open-source (or even source-available) project will include all the necessary build scripts and instructions needed for rebuilding it anyway, and it will be portable enough that this process isn’t tied down to a non-public CI environment.

If you’re asking exactly how much of this you can legally get away with omitting from a project using an LGPL library, then (a) you’re clearly not interested in providing a good open-source project, and (b) you should probably consult a lawyer rather than looking for free armchair legal advice from the community that you’re trying to avoid contributing to.

Re:Sequoia PGP is now LGPL 2.0 by lmm on Tuesday October 19, 2021 @01:44AM (#28915216)
The license text just requires that the user "can" do it: "Accompany the work... with the complete machine-readable "work that uses the Library", as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library." Interpreting that is a question for the court; I would speculate that manual instructions are probably good enough as long as you provide instructions that actually work.
Re:Sequoia PGP is now LGPL 2.0 by thaumasiotes on Tuesday October 19, 2021 @02:15AM (#28915328)
> I would speculate that manual instructions are probably good enough as long as you provide instructions that actually work.

Well, as long as the instructions rely only on things to which the user has access. If you document your internal build system beautifully, and nobody else is allowed to use it, that would not seem to pass muster.

Re:Sequoia PGP is now LGPL 2.0 by jcelerier on Tuesday October 19, 2021 @01:09AM (#28915057)
Entirely outside of the licensing debate, if your project only builds on a specific CI that's a huge engineering red flag I'd say