[PD-dev] overview of upstream sources?

[Martin Peach]

According to the FAQ at gnu .org
(http://www.gnu.org/licenses/gpl-faq.html#UnchangedJustBinary):
I downloaded just the binary from the net. If I distribute copies, do I
have to get the source and distribute that too?

Yes. The general rule is, if you distribute binaries, you must distribute
the complete corresponding source code too. The exception for the case
where you received a written offer for source code is quite limited.

...doesn't this imply that deken should also provide the source code
itself, at least as an option?

Martin

On Tue, Dec 22, 2015 at 8:07 AM, Roman Haefeli <reduzent at gmail.com> wrote:

> On Thu, 2015-12-17 at 19:20 +0100, Fred Jan Kraan wrote:
>
> > >
> > > I would rather propose adding some mandatory meta information to deken
> > > uploads. A package that can be downloaded from puredata.info should at
> > > least contain the information which sources it was built from.
> >
> > The puredata.info could host such a list in the public wiki.
> >
> > It is not very convenient to download several packages just to find out
> > the most recent/bug free.
>
> Exactly. This is why there is a version field in deken packages.
>
> I don't see how something like a fork map helps the end user, i. e. the
> one using Pure Data and installing an external through deken. When you
> install something with deken, you primarily want to know what sources
> have been used to build that package. Once you know that, you might also
> want to know where those sources are forked from. Currently, you only
> know _who_ as uploaded a package, but you do not know _where_ the
> sources of a package are hosted.
>
> I'm not opposing the idea of a fork map, but there is more important
> information missing before that.
>
> Roman
>
> _______________________________________________
> Pd-dev mailing list
> Pd-dev at lists.iem.at
> http://lists.puredata.info/listinfo/pd-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-dev/attachments/20151222/ef03d67e/attachment.html>