Hi Quim Gil,
When I wrote that I was not with nokia company in my mind but the
maemo community that is made by people. I know that there is no free
lunch, and many (most?) of this community is being payed to work on
this platform, but I was thinking in free time contributing, that is
common in
Hi Rodrigo,
On Tue, 2007-08-07 at 19:57 -0300, ext Rodrigo Vivi wrote:
Hi Quim Gil,
When I wrote that I was not with nokia company in my mind but the
maemo community that is made by people.
No problem! I wasn't seeing you as anything different as community. In
fact I wasn't answering to you
Hi,
ext Kees Jongenburger wrote:
From my point of view as user as you call them has no access to the
sbuild/buildd/debuild system, they get an sdk and that's it, Creating
an improved dh_make , recompiling the package to use the thumb
instruction set or not, are simply not part of the things
On 8/6/07, Eero Tamminen [EMAIL PROTECTED] wrote:
Hi,
ext Kees Jongenburger wrote:
From my point of view as user as you call them has no access to the
sbuild/buildd/debuild system, they get an sdk and that's it, Creating
an improved dh_make , recompiling the package to use the thumb
not make
it easy to do either. I hope that this will improve in the future.
just having a public maemo repository is not enough.
% dh_make
% debuild -us -uc (or, if you have a broken Scratchbox:
dpkg-buildpackage -rfakeroot -us -uc)
And debs appear. They'll work, but probably won't build
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Stone schreef:
(That our SDK could certainly be improved
is a separate issue as to whether we should use OE/BitBake or Debian
packages.)
Again, that is not an 'or', OE is perfectly capable of creating debian
packages, as the
Mamona distro
ext Koen Kooi [EMAIL PROTECTED] writes:
To summarize the differences:
* OE is a build and packaging tool
* Scratchbox is a development tool
Hmm:
http://www.openembedded.org/
OpenEmbedded is a full-featured development environment [...]
:-)
Hi Marius,
I'll call by end user those developers that use the distro/SDK to
develop their programs and by developer those that are coding the
distro/SDK itself.
OE makes developer's life easier because under OE repository there are
a lot of package descriptions and tasks definitions that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rodrigo Vivi schreef:
Some Months ago Koen said me a truth:
Hackers like to code and don't want to spend their time packing
To summarize the differences:
* OE is a build and packaging tool
* Scratchbox is a development tool
They overlap in the
ext Rodrigo Vivi [EMAIL PROTECTED] writes:
On 7/23/07, Marius Vollmer [EMAIL PROTECTED] wrote:
[...] Can't we just wait for Ubuntu Mobile?
I don't believe that wait is a good approach.
Yep, I agree. With waiting for Ubuntu Mobile I meant to wait for it
to emerge enough that we can join
On 7/27/07, Koen Kooi [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rodrigo Vivi schreef:
Some Months ago Koen said me a truth:
Hackers like to code and don't want to spend their time packing
To summarize the differences:
* OE is a build and packaging tool
*
On Fri, Jul 27, 2007 at 11:36:55AM -0300, ext Rodrigo Vivi wrote:
I'll call by end user those developers that use the distro/SDK to
develop their programs and by developer those that are coding the
distro/SDK itself.
OE makes developer's life easier because under OE repository there are
a
Er, how is this different from Debian, where you have a number of
package descriptions and task definitions that sbuild/buildd/debuild
uses to build? (Bearing in mind that debian/rules is a Makefile, and
thus infinitely flexible.)
What kind of step does a user have to take between creating
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rodrigo Vivi wrote:
I don't believe that wait is a good approach. If we believe and
conclude that Ubuntu Mobile will be a good alternative we need to join
and help the Ubuntu community to do that. This kind of contribution
that makes the free
On 7/23/07, Marius Vollmer [EMAIL PROTECTED] wrote:
ext Kees Jongenburger [EMAIL PROTECTED] writes:
from what I understand it' maemo that has been assembled from well
known wood sources (debian/linux/glib/gtk). I just can't imagine that
you could have been that creative/productive with
ext Kees Jongenburger [EMAIL PROTECTED] writes:
from what I understand it' maemo that has been assembled from well
known wood sources (debian/linux/glib/gtk). I just can't imagine that
you could have been that creative/productive with hildon if you also
had to manage external
ext [EMAIL PROTECTED] [EMAIL PROTECTED] writes:
Ok, let me go once again back to this boat analogy.
Be sure to understand that an anology is not a model for reality. You
can't use it to predict how reality will behave. It is just an aid to
talk about reality.
Maybe because the whole concept
Ok, let me go once again back to this boat analogy. I wasn't in the
early days of this project so I really don't know the detals of the
first decisions, but I still see that the options chosen probably made a
lot of sense on that time.
Maybe because the whole concept
of something that is
Hi,
I'm a Debian Developer participating in Debian GNOME packaging and
interested in the packaging of maemo apps.
On Fri, Jul 20, 2007, [EMAIL PROTECTED] wrote:
[...] But a non-stable repository is
something different: a tool for developers.
[...]
Hi Loïc,
The first reason Nokia / Maemo might want to offer an
unstable repository is quite certainly to ease developer
participation. But I think there are two things which you're
developing at the same time:
- upstream development of some software (especially Hildon, misc N800
apps
Hi,
But you can give users the choice to select option to install
from unstable repository which may contain OS upgrade packages
and this practice is ordinary.
We have already announced our plans to allow updated via packages
instead of having to reflash the device. This feature implies the
The steps for us to put this maemo unstable repository in place are
not ordinary at all. Create and maintain a public repository is not
an ordinary task in general. There must be clear reasons to do that
and a crystal clear collection of needs and requirements.
Change means work and there
We didn't start out with a distribution and now fixing this of course
means work to implement the changes. This work is mainly caused by
missing the boat in the first place, in my opinion. The boat was
there but we decided to swim instead. Maybe because the whole concept
of something that
23 matches
Mail list logo
