On Sat, Jul 11, 2015 at 10:01 AM, wrote:
> On 2015-07-10 09:39 Chris Warrick wrote:
>> And you should not create the files in your install script. Instead,
>> install them to a different data dir (somewhere in 'share/appname', or
>> alongside your package). When someone runs your app, only then
On 2015-07-10 09:39 Chris Warrick wrote:
> And you should not create the files in your install script. Instead,
> install them to a different data dir (somewhere in 'share/appname', or
> alongside your package). When someone runs your app, only then you
> should copy this file to user’s config di
Hi Chris,
thank you for your answer.
On 2015-07-10 09:39 Chris Warrick wrote:
> You should NEVER use sudo with pip. Instead, use virtualenvs as a
> regular user, or create your own .deb packages.
I am not sure, but maybe this is an Ubuntu-specific "problem"?
When I don't use sudo I got error
CC’ing the mailing list; please use Reply All in the future.
On 10 July 2015 at 16:36, wrote:
> Hi Chris,
>
> thank you for your answer.
>
> On 2015-07-10 09:39 Chris Warrick wrote:
>> You should NEVER use sudo with pip. Instead, use virtualenvs as a
>> regular user, or create your own .deb pa
On 10 July 2015 at 03:11, wrote:
> I am using setuptools to create a wheel file.
>
> There is a conf-file I want to install into the users config-diretory.
> e.g. /home/user/.config/appname/app.conf
>
> setup(...,
> data_files = [ ('~/.config/appname/', ['app.conf']) ]
> )
>
> I see tw
I am using setuptools to create a wheel file.
There is a conf-file I want to install into the users config-diretory.
e.g. /home/user/.config/appname/app.conf
setup(...,
data_files = [ ('~/.config/appname/', ['app.conf']) ]
)
I see two problems here:
1.
I don't know the users "name".
