nd long after
we have replaced the binaries with new versions. We have no mechanism
in place for this.
In addition, this requirement is placed on the maintainer, who must be
prepared to fulfill it even if something happens to the Debian project.
Richard Braakman
P.S. You can find a copy at <http:/
Philip Hands wrote:
> Richard Braakman <[EMAIL PROTECTED]> wrote:
> > This means that if we distribute modified versions of an NPL'd
> > program, we're going to have to keep source packages around long after
> > we have replaced the binaries with new version
Philip Hands wrote:
> > Richard Braakman <[EMAIL PROTECTED]> wrote:
> > Yeah, but that's only option b). You also have option a), which is to
> > distribute binary and source together, like we do. Then you can drop
> > the source as soon as you drop the
on. A release
> manager/group that is doing its job should have an easy time
> maintaining this page, in large part because they make the final
> decision on what goes into a release.
Indeed, but I am not necessarily aware of everything that gets done
during the development period. I'm more likely to notice when there
are problems with something :)
Richard Braakman
for all to use, they don't
want to see others build on their work without giving the same
favour back.
Richard Braakman
5 matches
Mail list logo
