On Aug 09, 2015, at 10:15 AM, Steve M. Robbins wrote:
>In my defense: I did not say you need to use "sudo". All you need (at least
>for pyvtk) is privilege to write into /usr/local, so it is more like "rm -rf
>/usr/local" ... still damaging but not as dramatic. :-)
pip --user (no sudo) is fin
On August 8, 2015 10:13:04 AM Piotr Ożarowski wrote:
> [Steve M. Robbins, 2015-08-08]
>
> > I went looking for the most recent sources and found out that you
> >
> > can easily get pyvtk via pip.
>
> `sudo pip install ...` is the same as `rm -rf /` to me.
I see.
> Please don't suggest it!
❦ 9 août 2015 13:46 +0200, Lennart Weller :
>> Everything looks good except the LICENSE.txt which is not here. It is in
>> fact called LICENSE upstream and it should be added to the manifest to
>> be present in the tarball. A note to upstream would be nice. Add a
>> comment to debian/copyright
>> I fixed those. I didn't add Vcs yet as I hadn't uploaded it to Alioth. I
>> just set them to my git hosting for now and will change them when the
>> upload is done. Same with the Maintainer field.
>
> Everything looks good except the LICENSE.txt which is not here. It is in
> fact called LICENSE
4 matches
Mail list logo
