On 12/13/2010 01:30 AM, ext David Greaves wrote:
Can I ask how this applies to the 50+ packages which are currently part of meego
but which are opensource and many of which we presumably expect to be used
elsewhere?
eg:
libmeegochat
libmeegotouch
maemo-meegotouch-interfaces (!)
meego-handset-*
Hi, let's see if we can move into specific details to find and fix whatever is
problematic in this discussion about using anything close to meego in
packages and distro names.
About using meego or something similar to name a distro using MeeGo related
components, the opinion of The Linux
On Tue, 14 Dec 2010, quim@nokia.com wrote:
About package names, since they are open source (LGPL,
Apache...) there shouldn't be any problems redistributing
them with the same name, isn't it. If there is a problem
with the name or license of a specific package please
let's file a bug
On 12/14/2010 7:57 AM, quim@nokia.com wrote:
Hi, let's see if we can move into specific details to find and fix whatever is
problematic in this discussion about using anything close to meego in
packages and distro names.
Can that discussion *PLEASE* move away from the development list
Hi all,
I was wondering if there exists a migration path from MeeGo 1.0 to MeeGo 1.1
and later to MeeGo 1.2. This is very interesting for companies that have
devices in the field and want to push an upgrade to the next higher version
(instead of just an update within a version).
Is it just a
- Original message -
From: quim@nokia.com
To: meego-dev@meego.com
Subject: [MeeGo-dev] Using meego or similar in packages and distro
names
Date: Tue, 14 Dec 2010 15:57:01 +
�
Progress in this discussion is measured in improvements to the
current documentation and bugs
On Di, 2010-12-14 at 08:35 -0800, Arjan van de Ven wrote:
On 12/14/2010 7:57 AM, quim@nokia.com wrote:
Hi, let's see if we can move into specific details to find and fix whatever
is problematic in this discussion about using anything close to meego in
packages and distro names.
On 12/14/2010 8:47 AM, Julian Andres Klode wrote:
On Di, 2010-12-14 at 08:35 -0800, Arjan van de Ven wrote:
On 12/14/2010 7:57 AM, quim@nokia.com wrote:
Hi, let's see if we can move into specific details to find and fix whatever is
problematic in this discussion about using anything close
Hello,
Deployed an application in MeeGo 1.1 but it doesnot show up in list of
applications installed.
However I can lanuch the app from terminal.
Here is application packaging information:
/usr/bin/application binary
/usr/share/applications/hildon/application.desktop
Em Terça-feira, 14 de Dezembro de 2010, às 16:45:28, Jechlitschek, Christoph
escreveu:
Hi all,
I was wondering if there exists a migration path from MeeGo 1.0 to MeeGo 1.1
and later to MeeGo 1.2. This is very interesting for companies that have
devices in the field and want to push an upgrade
On Dec 14, 2010, at 8:45 AM, Jechlitschek, Christoph wrote:
Hi all,
I was wondering if there exists a migration path from MeeGo 1.0 to MeeGo 1.1
and later to MeeGo 1.2. This is very interesting for companies that have
devices in the field and want to push an upgrade to the next higher
Hi,
nanjundiah.har...@elektrobit.com wrote:
Deployed an application in MeeGo 1.1 but it doesnot show up in list of
applications installed.
However I can lanuch the app from terminal.
This implies that the .desktop file is not being parsed by the desktop,
or it is missing some crucial
Hi,
Just noticed that http://wiki.meego.com/Core_OS_Program/Kernel_policy
came up and is on the agenda for TSG meeting tomorrow, so given that
we have 24 hours to comment and I haven't seen it discussed in public,
here's a couple of questions/comments from a hardware adaptation PoV
(not speaking
On 12/14/2010 1:45 PM, Carsten Munk wrote:
Hi,
Just noticed that http://wiki.meego.com/Core_OS_Program/Kernel_policy
came up and is on the agenda for TSG meeting tomorrow, so given that
we have 24 hours to comment and I haven't seen it discussed in public,
here's a couple of questions/comments
On 12/14/2010 2:38 PM, Nishanth Menon wrote:
Carsten Munk had written, on 12/14/2010 03:45 PM, the following:
btw, I think this discussion is better on meego-kernel ML.
Just noticed that http://wiki.meego.com/Core_OS_Program/Kernel_policy
Overall, meaning of upstream is confusing to me at
Arjan van de Ven had written, on 12/14/2010 04:55 PM, the following:
[...]
1. MeeGo will ship with one 'reference kernel', that will have one
shared codebase
between all the devices it supports (with different configuration
files). This kernel will be close to the upstream kernel with very
few
On 12/14/2010 3:10 PM, Nishanth Menon wrote:
Arjan van de Ven had written, on 12/14/2010 04:55 PM, the following:
[...]
1. MeeGo will ship with one 'reference kernel', that will have one
shared codebase
between all the devices it supports (with different configuration
files). This kernel will
Arjan van de Ven had written, on 12/14/2010 05:14 PM, the following:
On 12/14/2010 3:10 PM, Nishanth Menon wrote:
Arjan van de Ven had written, on 12/14/2010 04:55 PM, the following:
[...]
1. MeeGo will ship with one 'reference kernel', that will have one
shared codebase
between all the
On 12/14/2010 3:34 PM, Nishanth Menon wrote:
a relatively current release will be chosen yes. Now last formal is
a hard term; since 2.6.38 likely will be out before 1.2 ships, 2.6.37
is clearly not the last formal release at the time of ship.
(but 2.6.38 will be out very shortly before 1.2
Since this goes into some gconf setting in meego... trying meego-dev as
well, does anyone know how the target device profile gets specified
post 1.1?
Thanks.
===
Hi all,
On MeeGo 1.1, we used to modify the gconf setting of
/meegotouch/theme/target to point
hi, all guys,
when installing , there are only five fs --- btrfs,
ext2, ext3, vfat , nfs-- to select, and if you choose ext3 or other type to
/ , there will be a warning to tell you , the rootfs can only be btrfs;
however, I need ext4 to be supported and more, I want to format root
hi~~
Sensorfw can not load the compass sensor plugins.
And I find a README file in sensorfw , include a information about the
problem.
When does the compass sensor plugins would built in the sensorfw package??
Thanks.
___
MeeGo-dev mailing list
On Tue, Dec 14, 2010 at 03:14:06PM -0800, Arjan van de Ven wrote:
On 12/14/2010 3:10 PM, Nishanth Menon wrote:
Arjan van de Ven had written, on 12/14/2010 04:55 PM, the following:
[...]
1. MeeGo will ship with one 'reference kernel', that will have
one shared codebase
between all the
Hi,
nanjundiah.har...@elektrobit.com wrote:
Deployed an application in MeeGo 1.1 but it doesnot show up in list of
applications installed.
However I can lanuch the app from terminal.
This implies that the .desktop file is not being parsed by the desktop,
or it is missing some crucial
On Tue, 2010-12-14 at 23:37 +0200, Dave Neary wrote:
Hi,
nanjundiah.har...@elektrobit.com wrote:
Deployed an application in MeeGo 1.1 but it doesnot show up in list of
applications installed.
However I can lanuch the app from terminal.
This implies that the .desktop file is not
25 matches
Mail list logo
