Author Topic: Build System / Other Ipk Feeds  (Read 4298 times)

realm

  • Jr. Member
  • **
  • Posts: 79
    • View Profile
    • http://
Build System / Other Ipk Feeds
« on: June 03, 2007, 08:57:58 am »
over the past few weeks i've been playing with pdaxrom's build system and getting more comforable with it. i'm noticing though that of all the new packages that people are taking the time to build that when i sync with svn they never get added to the central repository, so when a new release is done everyone has to re-do / re-figure everything out again.

It seems we could stop repeating alot of the same work if we added these to the pdaxrom build system so once a package is in it just needs updated and rebuilt there. I'll gladly submit the package updates i've done, and i'd like to be able to add the new packages i'm working on into the main feed.
SL-C860   r197
SL-C3000 Angstrom with e17 /1 Gig SD/Senao Wifi/CF Bluetooth/CF GPS

InSearchOf

  • Administrator
  • Hero Member
  • *****
  • Posts: 1144
    • View Profile
    • http://
Build System / Other Ipk Feeds
« Reply #1 on: June 03, 2007, 09:56:22 am »
There are only a select few users that can commit (as you say "sync") to svn. They are the pdaXrom Devs. Packages that is built buy users are not added to the build system unless one of the devs has time and/or feels as if this is a significant application.

Yes it would be nice to have every package built by the community in the builder... but that would be a job by itself... we will look at adding alot of the packages that are built in... but to save us time maybe the community can start listing there packages with dependancies, build options, and any patches.

Late
Sharp Zaurus SL-C3100 and SL-6000L
pdaXrom Developer
Please visit pdaXrom.org for updates
My Blog
IRC #pdaxrom @ FreeNode

realm

  • Jr. Member
  • **
  • Posts: 79
    • View Profile
    • http://
Build System / Other Ipk Feeds
« Reply #2 on: June 03, 2007, 10:51:00 am »
where do you want us to submit our .make and .in files for the builder to speed you along?
SL-C860   r197
SL-C3000 Angstrom with e17 /1 Gig SD/Senao Wifi/CF Bluetooth/CF GPS

psycoman

  • Jr. Member
  • **
  • Posts: 75
    • View Profile
    • http://www.tuxforum.com.br
Build System / Other Ipk Feeds
« Reply #3 on: June 03, 2007, 11:05:13 am »
why not make a central feed in tyrannozaurus ?  ^^

desertrat

  • Hero Member
  • *****
  • Posts: 743
    • View Profile
    • http://
Build System / Other Ipk Feeds
« Reply #4 on: June 03, 2007, 11:16:24 am »
Quote
It seems we could stop repeating alot of the same work if we added these to the pdaxrom build system so once a package is in it just needs updated and rebuilt there. I'll gladly submit the package updates i've done, and i'd like to be able to add the new packages i'm working on into the main feed.
That is a subject I had been meaning to raise. It would be extremely nice to have a central repository where we could submit "recipes". This would eliminate a lot of duplicate work, particularly when packages depend on certain (updated) versions of libraries. However I guess it would take a huge amount of administrative effort to ensure that all the "recipes" will work with each other.
SL-C3100 / Ambicon WL1100C-CF / pdaXrom 1.1.0beta3 / IceWM

realm

  • Jr. Member
  • **
  • Posts: 79
    • View Profile
    • http://
Build System / Other Ipk Feeds
« Reply #5 on: June 03, 2007, 11:52:21 am »
Quote
why not make a central feed in tyrannozaurus ?  ^^
[div align=\"right\"][a href=\"index.php?act=findpost&pid=162477\"][{POST_SNAPBACK}][/a][/div]

right now people are locked into a given release of pdaxrom because their key apps they want were built by someone on their own and released against the given lib's in that release. this type of thing can be ended if the packages get added to the main feed.

another feed isn't going to centralize the distro package management, when then main feed is built the central apps, like firefox, optimized mplayer, and openoffice should all be built with the main feed, and have their current recipie so anyone can check out the subversion repository and if they want pdaxrom built around libc 2.3.6 instead of 2.2.5. Then all they should have to do is pull down the latest version configure the toolchain, build configure the rom, build make the image and be set to go, as it stands now most of the key packages are built outside of the build system, so even if you built a seperate system, you'd still have to work past the quirks of other packages you want to have installed.
SL-C860   r197
SL-C3000 Angstrom with e17 /1 Gig SD/Senao Wifi/CF Bluetooth/CF GPS

InSearchOf

  • Administrator
  • Hero Member
  • *****
  • Posts: 1144
    • View Profile
    • http://
Build System / Other Ipk Feeds
« Reply #6 on: June 03, 2007, 02:36:25 pm »
I agree 100%... but like I said... that would be a fulltime job for one of the devs... One thing I do know is that most people that build apps use the zgcc.img to and build them natively on the Z.

That will have to be a task done after I get the kernel stuff worked out.

Late
Sharp Zaurus SL-C3100 and SL-6000L
pdaXrom Developer
Please visit pdaXrom.org for updates
My Blog
IRC #pdaxrom @ FreeNode

realm

  • Jr. Member
  • **
  • Posts: 79
    • View Profile
    • http://
Build System / Other Ipk Feeds
« Reply #7 on: June 03, 2007, 03:13:24 pm »
once we get to where we can pull a fully functional build system down that spits out the base rom i'll gladly take up a list of packages people want in the main feed and send them to whichever dev you want to look over them.

thats probably a ways off though, so what can i provide you with to get us there? do you just want lists of package / dependancies / where to get / compile options, or do you want the .make and .in files generated from the NEWPACKAGE script and modified with the dependancies src and compile options?
SL-C860   r197
SL-C3000 Angstrom with e17 /1 Gig SD/Senao Wifi/CF Bluetooth/CF GPS