Teemu Ikonen writes (Re: Bug#426581: meshlab - anyone still working on this):
The package has not been updated to 1.1.1, and I may not have time to
do it very soon. Ian did promise to sponsor the package, but I haven't
heard anything from him lately.
I do exist but don't let me stop anyone
On Fri, Apr 4, 2008 at 6:21 PM, Teemu Ikonen [EMAIL PROTECTED] wrote:
On Fri, Apr 4, 2008 at 4:15 PM, Yaroslav Halchenko
[EMAIL PROTECTED] wrote:
So what was the outcome? ;-) 1.1.1 upstream is out but ITP is still
open. Is help/sponsoring needed?
Ok, I updated the package to 1.1.1, it
So what was the outcome? ;-) 1.1.1 upstream is out but ITP is still
open. Is help/sponsoring needed?
On Mon, 17 Mar 2008, Teemu Ikonen wrote:
On Sat, Mar 8, 2008 at 7:00 PM, Paolo Cignoni [EMAIL PROTECTED] wrote:
we are going to release the v1.1.1 of meshlab
and i have arranged the source
On Sat, Mar 8, 2008 at 7:00 PM, Paolo Cignoni [EMAIL PROTECTED] wrote:
we are going to release the v1.1.1 of meshlab
and i have arranged the source with hopefully all the issues that you
have raised.
Before releasing officially , could you check that the following sources are
ok?
Paolo Cignoni writes (Re: Bug#426581: meshlab - anyone still working on this):
We use QT with QSettings mechanism for saving config files in a portable way
Can these files be written other than by Qt ? Our configuration
management systems often need to write to configuration in situations
where
El Miércoles 27 Febrero 2008, Ian Jackson escribió:
Paolo Cignoni writes (Re: Bug#426581: meshlab - anyone still working on
this):
We use QT with QSettings mechanism for saving config files in a portable
way
Can these files be written other than by Qt ?
Yes, they are xml files
El Domingo 24 Febrero 2008, Paolo Cignoni escribió:
[snip]
So a possible reasonable, solution is that i detect at compile time if
you are compiling meshlab on a debian system, and ONLY in that case,
disable any phoning home option. Adding a compile time option would be
something that a lazy
On Sun, Feb 24, 2008 at 2:54 PM, Ian Jackson
[EMAIL PROTECTED] wrote:
Paolo Cignoni writes (Re: Bug#426581: meshlab - anyone still working on
this):
Yes, it phones home regularly.
It is well written in the docs
http://meshlab.sourceforge.net/wiki/index.php/Licenses
Thanks
Paolo Cignoni writes (Re: Bug#426581: meshlab - anyone still working on this):
Ok, I understand your point, I respect and, as i told you since
beginning, i agree on disabling it for very pure, and ethically
coherent distributions like Debian.
As you understood, this data collecting
Lisandro Damián Nicanor Pérez Meyer writes (Re: Bug#426581: meshlab - anyone
still working on this):
Is it possible to add this behaviour as a separate package? I mean, like the
debian-populaity-contest. Or, when you are installing the package, ask the
user if [s]he wants to enable it.
Yes
On Sun, Feb 24, 2008 at 6:42 PM, Ian Jackson
[EMAIL PROTECTED] wrote:
Paolo Cignoni writes (Re: Bug#426581: meshlab - anyone still working on
this):
Ok, I understand your point, I respect and, as i told you since
beginning, i agree on disabling it for very pure, and ethically
coherent
(shortened and with intermixed answers...)
On Fri, Feb 22, 2008 at 10:00 PM, Ian Jackson
[EMAIL PROTECTED] wrote:
Paolo Cignoni writes (Re: Bug#426581: meshlab - anyone still working on
this):
After I built it (on lenny), I ran meshlab from an xterm. It opened
an entirely blank override
On Fri, Feb 22, 2008 at 10:06 PM, Ian Jackson
[EMAIL PROTECTED] 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
Paolo == Paolo Cignoni [EMAIL PROTECTED] writes:
Paolo Yes, it phones home regularly.
[snip]
Paolo In any case i need this
Paolo feature so i could disable it but only for Debian builds.
Paolo Is it possible to know at compile time if the runnining
Paolo system is a 100%
Paolo Cignoni writes (Re: Bug#426581: meshlab - anyone still working on this):
I am a bit ignorant about debian package creation so be patient with my
naiveness :)
I would try to help as I can.
My comments intermixed below.
Thanks for your reply and sorry for the delay in getting back to you
Teemu Ikonen writes (Re: Bug#426581: meshlab - anyone still working on this):
Thanks for the review. I fixed the problems you found except these:
After I built it (on lenny), I ran meshlab from an xterm. It opened
an entirely blank override-redirect pale grey window covering the top
left
Teemu Ikonen writes (Fwd: Bug#426581: meshlab - anyone still working on this):
Since you asked about meshlab packages a while ago, are you still
interested in sponsoring them? I have packages ready for review, see
the mail below for details.
Thanks.
Teemu Ikonen [EMAIL PROTECTED] writes
Teemu Ikonen writes (Re: Bug#426581: meshlab - anyone still working on this):
http://esko.osmas.info/~tmx/meshlab/
I've reviewed this and it's looking reasonably good.
Firstly, two general observations:
* You should run lintian, particularly after making a wholly new
package.
* With a new
Hi to all,
I am a bit ignorant about debian package creation so be patient with my
naiveness :)
I would try to help as I can.
My comments intermixed below.
(Thanks for your effort!)
After I built it (on lenny), I ran meshlab from an xterm. It opened
an entirely blank override-redirect pale
19 matches
Mail list logo
