[maemo-developers] Public maemo repository

From: Daniel Stone daniel.stone at nokia.com
Date: Mon Jul 30 13:58:01 EEST 2007
On Fri, Jul 27, 2007 at 09:14:09PM +0200, ext Kees Jongenburger wrote:
> > 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 it's own
> package and the sbuild/buildd/debuild aproach? isn't this hole
> open-source thingy about giving power to the user?

It depends entirely on the tools.  You could easily construct an
improved dh_make that required no editing of any files at all.  It has
nothing to do with the packaging system itself, as cdbs's three-line
debian/rules files have shown.

> > Sounds like a recipe for crap packages to me (maybe OE's are good, I
> > don't actually know).  If you want incredibly basic skeleton packages,
> > just use the dh_make template and ignore them, and the packages won't be
> > any good.  If you want to fix them up so they conform to policy, are
> > more generally useful, are split as they should be, etc, then you'll
> > need to spend time on your packages.
> If you are using dh_make you are not using the "power" of the existing
> debian packages and you are in trouble

Who was saying this?  Using dh_make is fine.  If you want your packages
to be good, then you should clean up the template a bit, yes.

> if you don't use dh_make and try to use upstream packages + patches
> you are in trouble because you are creating the chaos youself, You are
> also prooving that  the initial "source" packaging was not sufficient
> for your need

I don't see what you mean here?

> > This is no different from ebuilds, spec files, or any packaging system
> > I've ever used.  The only difference is that debian/ tends to be a
> > little more verbose for the skeleton case.  But the core is the same: if
> > you want crap packages, then you can easily create them in any packaging
> > system.  If you want good packages, then you need to spend a bit more
> > time.
> I think there is a big difference between those systems. Me as
> developer ,I have the same tools as you the packager (as I tend to
> call people who create packages)
> bsd ports,gentoo portage and oe contain meta packages.
> lets' face it what good did the packaging bring maemo until now? I
> don't understand I am still waisting my time with this packaging
> issue.

The possibly to derive from an existing system, not having to invent our
own packages or tools to solve problems that have already been taken
care of long ago?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.maemo.org/pipermail/maemo-developers/attachments/20070730/2058eb1d/attachment.pgp 
More information about the maemo-developers mailing list