On Sun 26 Sep 2010 12:37, Martin Grimme martin.gri...@gmail.com writes:
Hi,
in my experience the separate developer account doesn't work for all
stuff out of the box. The developer account lacks membership in some
Unix groups the regular user is member of.
Not anymore :)
On Wed, Sep 29, 2010 at 15:15, Tomi Ollila
tomi.oll...@guru.guru-group.fi wrote:
On Sun 26 Sep 2010 12:37, Martin Grimme martin.gri...@gmail.com writes:
in my experience the separate developer account doesn't work for all
stuff out of the box. The developer account lacks membership in some
On Mon, Sep 27, 2010 at 8:58 AM, ronan.maclave...@nokia.com wrote:
Earlier in the summer I tried with root using the password authentication
scheme - it worked. If you use user then you do not need to use the key
mechanism, the password does not change frequently like the developer
password.
2010/9/26 Ville M. Vainio vivai...@gmail.com:
Being able to set a breakpoint and actually hitting that breakpoint on
device without batting an eyelid is what IMO rocks most about the
whole Nokia Qt SDK scheme.
Oh yeah - I forgot about that. The whole debugging integration is
pretty helpful,
On 09/27/2010 03:37 PM, ext Thomas Perl wrote:
2010/9/26 Ville M. Vainiovivai...@gmail.com:
BTW, in new versions you can disable that packaging step (from build
settings, by expanding the Create Package build step). This makes
the deployment ~1 sec experience, which is pretty nice.
Thanks for
On 09/26/2010 06:26 PM, ext Ville M. Vainio wrote:
I just tried
- Giving password to user
- ssh in as user from terminal (success, answer yes to host id
query though).
- Test connection as user (success, qt versions listed)
- Deploy key as user, test the key authentication scheme
In my very limited personal experience from my first few hours with Qt Creator
yesterday, I can already tell you that it doesn't help in security at all:
I was browsing the example projects and decided to take a look at the calendar
example. Debugging it on the device caused it to replace the
Hi,
in my experience the separate developer account doesn't work for all
stuff out of the box. The developer account lacks membership in some
Unix groups the regular user is member of.
Regards,
Martin
2010/9/26, Thomas Waelti twae...@gmail.com:
In my very limited personal experience from my
On Sun, Sep 26, 2010 at 10:02 AM, Thomas Waelti twae...@gmail.com wrote:
In my very limited personal experience from my first few hours with Qt
Creator yesterday, I can already tell you that it doesn't help in security at
all:
I was browsing the example projects and decided to take a look at
On Wed, Sep 22, 2010 at 5:53 PM, Christian Kandeler
christian.kande...@nokia.com wrote:
That means that it doesn't use the information (databases etc.) stored
in the users home directory. I'm gradually starting to feel this is a
bad idea, that leads to subtle problems when developers are
On Wed, Sep 22, 2010 at 6:25 PM, Thomas Perl th.p...@gmail.com wrote:
The current version of Qt SDK automatically creates and deploys a .deb
on the device, so once the package has been deployed, if I want to
test the app with the user account, I just run it from X Terminal
Hi,
Earlier in the summer I tried with root using the password authentication
scheme - it worked. If you use user then you do not need to use the key
mechanism, the password does not change frequently like the developer
password.
(I haven't tried the user account or the key scheme with any
Hi
Original idea behind 'developer' account was to have separate filesystem
space where to experiment things -- and to get feedback what works and
what doesn't.
First iterations even had different uid for developer but that did not
work at all (x clients did not start, among other things ;/)
As many of you go, Nokia Qt SDK uses, through MADDE, a special
'developer' account (with it's own home directory) to do stuff on the
device
That means that it doesn't use the information (databases etc.) stored
in the users home directory. I'm gradually starting to feel this is a
bad idea, that
On Wed, Sep 22, 2010 at 1:35 PM, Ville M. Vainio vivai...@gmail.com wrote:
That means that it doesn't use the information (databases etc.) stored
in the users home directory. I'm gradually starting to feel this is a
bad idea, that leads to subtle problems when developers are trying to
pretend
On Wed, Sep 22, 2010 at 2:35 PM, Ville M. Vainio vivai...@gmail.com wrote:
As many of you go, Nokia Qt SDK uses, through MADDE, a special
'developer' account (with it's own home directory) to do stuff on the
device
That means that it doesn't use the information (databases etc.) stored
in
On Wed, Sep 22, 2010 at 1:45 PM, Attila Csipa ma...@csipa.in.rs wrote:
the less dangerous path. Some sort of clone/restore user data to developer
account *could* be useful though.
How hard will it be to copy stuff from /home/user to /home/developer
and then re-copy it once MADDE test has
On Wed, Sep 22, 2010 at 2:52 PM, Sivan Greenberg si...@omniqueue.comwrote:
On Wed, Sep 22, 2010 at 1:45 PM, Attila Csipa ma...@csipa.in.rs wrote:
the less dangerous path. Some sort of clone/restore user data to
developer
account *could* be useful though.
How hard will it be to copy stuff
On Wed, Sep 22, 2010 at 3:01 PM, Attila Csipa ma...@csipa.in.rs wrote:
If there are no components that work with hardcoded usernames od uid/gids,
that would roughly be it (for files, which are the most common problem
IIUC). Services/daemons might get tricky but I suppose that is not a nearly
On Wed, Sep 22, 2010 at 3:13 PM, Ville M. Vainio vivai...@gmail.com wrote:
On Wed, Sep 22, 2010 at 3:01 PM, Attila Csipa ma...@csipa.in.rs wrote:
If there are no components that work with hardcoded usernames od
uid/gids,
that would roughly be it (for files, which are the most common
On Wed, Sep 22, 2010 at 2:30 PM, Attila Csipa ma...@csipa.in.rs wrote:
Considering all of this, I'm inclined to wish we had a I know what
I'm using, please run this app as 'user'| checkbox in Nokia Qt SDK.
Hey, I'm always for options :) But the point is that a non-destructive way
of playing
On Wed, Sep 22, 2010 at 12:35, Ville M. Vainio vivai...@gmail.com wrote:
As many of you go, Nokia Qt SDK uses, through MADDE, a special
'developer' account (with it's own home directory) to do stuff on the
device
Indeed.
That means that it doesn't use the information (databases etc.) stored
On 09/22/2010 01:52 PM, ext Sivan Greenberg wrote:
How hard will it be to copy stuff from /home/user to /home/developer
and then re-copy it once MADDE test has finished? My guess a mere
shell command ?
I'm already looking forward to the bug reports from users who complain
that starting up a
On 09/22/2010 01:35 PM, ext Ville M. Vainio wrote:
As many of you go, Nokia Qt SDK uses, through MADDE, a special
'developer' account (with it's own home directory) to do stuff on the
device
That means that it doesn't use the information (databases etc.) stored
in the users home directory. I'm
2010/9/22 Christian Kandeler christian.kande...@nokia.com:
From Qt Creator's side, nothing prevents you from just giving the user name
user instead of developer in the Maemo device configuration. The only
problem is then accessing that account; if I'm not much mistaken, login is
disabled for
2010/9/22 Ville M. Vainio vivai...@gmail.com:
Considering all of this, I'm inclined to wish we had a I know what
I'm using, please run this app as 'user'| checkbox in Nokia Qt SDK.
The current version of Qt SDK automatically creates and deploys a .deb
on the device, so once the package has
26 matches
Mail list logo
