Bug#426581: meshlab - anyone still working on this
On Fri, Feb 22, 2008 at 10:06 PM, Ian Jackson
<ian@davenant.greenend.org.uk> wrote:
> Teemu Ikonen writes ("Re: Bug#426581: meshlab - anyone still working on this"):
>
> However I have discovered one thing that we in Debian ought to
> consider release-critical: I have discovered that the program prompted
> me that a new version had been released. This is presumably achieved
> by contacting some upstream server to check.
>
> Paulo, is that correct ?
>
> I'm afraid that it is not acceptable for a program packaged for Debian
> to phone home like this and that feature must be disabled before we
> upload it even to unstable.
>
Yes, it phones home regularly.
It is well written in the docs
http://meshlab.sourceforge.net/wiki/index.php/Licenses
in the windows installer users have to agree on that before the
installation begins.
It seems to me that it is not against the Debian social contract nor
against the Debian Free Software Guidelines (DFSG).
If I am wrong forgive my ignorance. In any case i need this feature so
i could disable it but only for Debian builds.
Is it possible to know at compile time if the runnining system is a
100% debian?
I mean, i need that feature, and disabling it for 'easy' distribution
like ubuntu seems me non very reasonable.
People installing skype could also tolerate meshlabs that phones home.
>
> > > If I run the program with --help or -h, it tries to open them as
> > > files. It ought at least to bomb out with a message saying please
> > > refer to the meshlab wiki (with a URL).
> >
> > Upstream.
>
> If I provide a patch will you incorporate it in your package ? I can
> do it as a bzr branch or an emailed diff, whichever you prefer. I
> think this is quite important. The behaviour atm is rather poor if
> you're trying just to figure out how to run the program.
>
An emailed diff is ok,
Thanks
P.
Reply to: