Author Topic: Pdaxrom Development  (Read 6336 times)

willgan

  • Jr. Member
  • **
  • Posts: 84
    • View Profile
    • http://
Pdaxrom Development
« Reply #15 on: July 24, 2006, 02:23:11 am »
well.. the fastest way to end this is to close this thread...

If you think OE fit u better than use OE.
If you think pdaxrom-builder fit u better than use pdaxrom-builder..
Why do you want to compare... which one is better..
We should work together and make programs to run smoothly (fitted nicely) in our Z, whether it is OZ or pdaxrom.

By the way, Sashz already open up for all who want to contribute..
« Last Edit: July 24, 2006, 02:28:01 am by willgan »
My Current Z...

Zaurus C1000 - Pdaxii13
Using Pdaxrom-builder (SVN) for building packages

iczer3

  • Jr. Member
  • **
  • Posts: 59
    • View Profile
Pdaxrom Development
« Reply #16 on: July 24, 2006, 02:44:27 am »
Dear Bundabrg,

Sorry for the mentioning in the post.
I just found it very tiring in reading so many posts in comparing
OE and Pdax that I did not recognize.

BR,

Felix.

koen

  • Hero Member
  • *****
  • Posts: 1008
    • View Profile
    • http://dominion.thruhere.net/koen/cms/
Pdaxrom Development
« Reply #17 on: July 24, 2006, 03:58:10 am »
Quote
OE is great however i have noticed that its main problems stem from people building distros straight from the package sources

there really needs to be a set standard for packaging and having OE turn itself into a distro in its own right, OR make it retargetable to have a "high" and "low" end target that slightly changes the compiling process, i assume it has somthing like gentoos make flags, (as i said eariler i neven got it to work properly) if so perhaps that should be given more enfisis along with a standard guide and template to packaging

I think you're misunderstanding how OE works and how distros use it. It seems you assume that every recipe generates the same package regardless of distro. That isn't true. You can have different patches per distro, different configure options per distro, different packaging per distro and different config files per distro. You can override anything you want per distro, per machine or both.

For example:

Code: [Select]
DEPENDS = "gtk+"
SRC_URI = "http://foo.com/bar-${PV}.tar.bz2"
SRC_URI_append_dablitzleetdist = "http://dablitz.com/extraleetness.patch;patch=1"
SRC_URI_append_pdax = "http://obscureurl.com/uglyhacks.patch;patch=1"

inherit autotools

EXTRA_OECONF_openzaurus = " --disable-leetnes"
EXTRA_OECONF_dablitzleetdist = " --enable-leetnes"
EXTRA_OECONF_pdax = " --only-work-at-full-moon"
EXTRA_OECONF_append_collie = " --enable-tinyscreenresolutions"
EXTRA_OECONF_append_akita = " --enable-OMGleetoverlayLOL"

CONFFILES_append_dablitzleetdist = "${sysconfdir}/leetnes.conf"

The above shows how one recipe produces different output for three distributions
and two machines. For the uninitiated: the above will download, patch, build, packages *and* add all dependencies to the resulting .ipk with a mere 'bitbake bar'.
Can you still say with a straight face it isn't retargetable?

Quote
the best thing to happen to it would be if a distro like debian picked it up  (now i am dreaming) as you would slowly get alot of packages and some sort of packaging guidelines

Check the  video of wookey's emdebian presentation at debconf2005[1]

And for the whiners in this thread: OE people will respond if you talk about OE, like pdaX people will respond if you talk about pdaX, get over it.

Pgas: I hope this is what you meant with 'show us examples instead of saying how great it is'

[1] http://meetings-archive.debian.net/pub/deb...emo-Wookey.mpeg
Forums are not bugtrackers!!! Smart questions
Ångström release team
iPAQ h2210, iPAQ h5550, iPAQ hx4700, Zaurus SL-C700, Nokia 770, all running some form of GPE
My blog

ofels

  • Full Member
  • ***
  • Posts: 139
    • View Profile
    • http://
Pdaxrom Development
« Reply #18 on: January 05, 2007, 07:43:53 am »
Quote
well.. the fastest way to end this is to close this thread...

If you think OE fit u better than use OE.
If you think pdaxrom-builder fit u better than use pdaxrom-builder..
Why do you want to compare... which one is better..
We should work together and make programs to run smoothly (fitted nicely) in our Z, whether it is OZ or pdaxrom.

Fortunately my profession gives me the chance to look at things from a deep technical and a user perspective.
The thing is that redundancy is not a very good way of creating software.
One might say that competition is good- however if competion is applied in a very small market like ours it ends up with going nowhere at all ind ht elong run because have to decide between two average products instead of a rather good one.

From what I have seen pdaxrom has created a good user environment with many interesting applications and a desktop like feeling. This environment is lacking with OE based distributions. Sure there is OPIE, but regarding new applications this looks like a dead end road without X capabilities though the existing applications are the most usable. There is GPE but it lacks the feeling for completeness and usability, enlightenment is complicated and bloated though powerful and fluxbox is well done but not finished without tweaking it manually. Those are lacking the overall feeling of an encapsulated environment pdaxrom seems to provide.
On the other hand there is OE with the possibility to almost automatically address a whole lot of distributions and devices and which makes it possible integrate and manage new software with minimum effort amongst a lot of other features.

OE could well be used to create its very own pdaxrom distribution but without loosing compatibility with OZ.  I can see a lot of people wasting a whole lot of efforts by redundantly creating the same thing: A mobile platform suited for daily usage. People which are not competing but engaged in some sort of rivalry and I would like to tell people to stop it. In fact this leads knowhere.  

Joining efforts would advance things a whole lot more  

Oliver