Oliver Grawert [2014-05-02 22:46 +0200]:
> how about making the usage of /etc/default/ mandatory for all our own
> services so we can easily disable them
Please please not. Parsing these has been a huge pain, source of bugs,
and unnecessary shell scriptery for a long time, in both the upstart
and
hi,
Am Samstag, den 03.05.2014, 10:00 +0200 schrieb Martin Pitt:
> Oliver Grawert [2014-05-02 22:46 +0200]:
> > how about making the usage of /etc/default/ mandatory for all our own
> > services so we can easily disable them
>
> Please please not. Parsing these has been a huge pain, source of bugs
hi,
Am Freitag, den 02.05.2014, 17:57 -0700 schrieb Steve Langasek:
> > how about making the usage of /etc/default/ mandatory for all our own
> > services so we can easily disable them ... i assume this interface will
> > also be still usable after the systemd transition somehow since it is
> > wid
hi,
Am Freitag, den 02.05.2014, 18:42 -0700 schrieb Steve Langasek:
> > 2. Although this thread originally mentions custom upstart jobs in
> > the context of carrier customizations, it should be noted that there
> > 22 existing system override jobs defined in our current Touch
> > images. These wi
Oliver Grawert [2014-05-03 11:42 +0200]:
> well, we either give access to the init system itself or we add
> something on top, i dont see whats wrong with using an established
> system for the second option
- It requires us to spawn a shell and parse a file, for something
which is already buil
Oliver Grawert [2014-05-03 11:35 +0200]:
> and yet you use it in apport for enabling/disabling the service ?
We actually don't any more. The file never changes any more (in the
distro), it's just there for historical reasons. default files were
the standard way to disable/re-enable services in th
hi,
Am Samstag, den 03.05.2014, 11:55 +0200 schrieb Martin Pitt:
> Oliver Grawert [2014-05-03 11:35 +0200]:
> However, I don't think you can get very far with *not* giving write
> access to customizers. There's hardly anything to customize then.
> Also, why would someone who wants to build a custom
Oliver Grawert [2014-05-03 13:14 +0200]:
> the customization kit is exactly for the purpose that everyone uses the
> same base image, has reliably the same bugs etc and can only customize
> what we allow.
Ah, thanks for the heads-up. So this is more like the "branding" kind
of customization, not l
On Sat, May 3, 2014 at 5:42 AM, Oliver Grawert wrote:
> hi,
> Am Freitag, den 02.05.2014, 17:57 -0700 schrieb Steve Langasek:
> > > how about making the usage of /etc/default/ mandatory for all our own
> > > services so we can easily disable them ... i assume this interface will
> > > also be sti
hi,
Am Samstag, den 03.05.2014, 13:26 +0200 schrieb Martin Pitt:
> Oliver Grawert [2014-05-03 13:14 +0200]:
> > the customization kit is exactly for the purpose that everyone uses the
> > same base image, has reliably the same bugs etc and can only customize
> > what we allow.
>
> Ah, thanks for t
hi,
Am Freitag, den 02.05.2014, 08:38 -0700 schrieb Alex Chiang:
> - mtp-server
this one is solely handled by the "persist.sys.usb.config" android
property, no need to reinvent the wheel by adding upstart override files
here, you just need to make sure that mtp is not set in this
property ... (we
On Sat, May 3, 2014 at 5:42 AM, Oliver Grawert wrote:
> hi,
> Am Freitag, den 02.05.2014, 17:57 -0700 schrieb Steve Langasek:
> > > how about making the usage of /etc/default/ mandatory for all our own
> > > services so we can easily disable them ... i assume this interface will
> > > also be sti
El 02/05/2014 08:38, "Dave Morley" escribió:
>
> On Fri, 2014-05-02 at 03:34 -0600, Selene Scriven wrote:
> > - Installing an app without a U1 account configured no longer
> > works. This is a regression. Tap the app, tap install, tap
> > "go to accounts" to configure a U1 account, and
On Fri, 2014-05-02 at 03:34 -0600, Selene Scriven wrote:
> - Installing an app without a U1 account configured no longer
> works. This is a regression. Tap the app, tap install, tap
> "go to accounts" to configure a U1 account, and then...
> nothing. Back to the app preview. H
On Fri, 2014-05-02 at 11:29 +0100, Alan Pope wrote:
> (although I can see a corner use case where you can pan apps left and
> right, one app plays through the left channel, another app through the
> right - it would keep my kids quiet in the back of the car when they
> share a set of headphones!)
The 'availables' list do not show on my N4 with utopic r9. No log
found in /var/crash.
On Fri, May 2, 2014 at 1:31 PM, Shuduo Sang wrote:
> On Tue, Apr 29, 2014 at 8:23 PM, Alejandro J. Cura
> wrote:
>> On Mon, Apr 28, 2014 at 9:25 PM, Shuduo Sang wrote:
>>> No core apps and suggestions show up
On Sun, 2014-05-04 at 10:36 +0800, Shuduo Sang wrote:
> The 'availables' list do not show on my N4 with utopic r9. No log
> found in /var/crash.
This may be due to bug #1307981 [1] or just that the search was
performed before network became available. You can check
~phablet/.cache/upstart/scope-re
On Sun, May 4, 2014 at 11:12 AM, Rodney Dawes
wrote:
> On Sun, 2014-05-04 at 10:36 +0800, Shuduo Sang wrote:
>> The 'availables' list do not show on my N4 with utopic r9. No log
>> found in /var/crash.
>
> This may be due to bug #1307981 [1] or just that the search was
> performed before network b
18 matches
Mail list logo
