supplierdeeply

New & orphan ports - what to do and when ?

  • 13 Replies
  • 1939 Views
  • Publish
    New & orphan ports - what to do and when ?
    « on: 23 / February / 2012, 22:24:38 »
    Advertisements
    I'm starting this thread to solicit comments about what we (as a community) want to do with new ports and orphan ports ? 

    When do we add a new port to the svn ?  And when does it become available in the autobuild server ?  As far as I can tell there are no rules or guidelines today - its more a gut feel call by the devs with svn commit access.  Which is okay with me as it stands - they do the work, can recognize good code when the see it, and handle the complaints.  And adding a new port is more complicated & time consuming than making a small patch.

    Also, what do we do about ports that kind of stall ?   (e.g. read the sx210is porting thread )   Do we capture the code "as is" in the svn in the hopes that somebody will pick it up at some point ?  (marked Alpha / SKIP_AUTOBUILD).  The links to download sites in the forum threads tend to expire - and the code is lost.  And even when not lost, it quickly gets out of date so that it does not build against the current svn.

    One issue here is code quality.  A port with lots of support and a good dev team is ideal.  What about the rest - how do we decide when a well meaning person struggling through the porting process for the first time has produced something to share with others ?

    Another thing to consider - there was a recent post about a porting effort that was near success with good  executable files posted when the dev had a hard drive crash and lost all his source.    A culture of early and frequent svn updates might have helped there.

    Or maybe we should just stay with the "survival of the fittest" we have now - ports that get released need to have one or more devs that take it all the way ?   Tends to ensure that what gets in the svn is fairly solid I think ?

    *

    Offline reyalp

    • ******
    • 9957
  • Publish
    Re: New & orphan ports - what to do and when ?
    « Reply #1 on: 23 / February / 2012, 23:25:04 »
    I've personally waffled on this a few times, but I'm generally in favor of getting the orphaned ports into SVN.
    Don't forget what the H stands for.

    *

    Offline philmoz

    • *****
    • 2936
      • Photos
  • Publish
    Re: New & orphan ports - what to do and when ?
    « Reply #2 on: 24 / February / 2012, 02:40:29 »
    I think it's better to get the code into SVN rather than risk losing it (it can always be removed later if needed).

    I'd also suggest adding one or more statuses (e.g. PRE_ALPHA) to help differentiate the state of the port.

    Phil.
    CHDK ports:
      sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
      g12 (1.00c, 1.00e, 1.00f & 1.00g)
      sx130is (1.01d & 1.01f)
      ixus310hs (1.00a & 1.01a)
      sx40hs (1.00d, 1.00g & 1.00i)
      g1x (1.00e, 1.00f & 1.00g)

  • Publish
    Re: New & orphan ports - what to do and when ?
    « Reply #3 on: 24 / February / 2012, 19:06:01 »
    I'd also suggest adding one or more statuses (e.g. PRE_ALPHA) to help differentiate the state of the port.
    Okay - I'll take a stab at it :

    1) pre-Alpha = code saved for reference, does not compile  -  SKIP_AUTOBUILD
    2) Alpha = code compiles, some functions not implemented or known not to work - SKIP_AUTOBUILD
    3) Beta = code compiles,  all functions implemented, testing needed
    4) Released = code in circulation for at least 4 weeks, all bugs from Beta stage corrected

    Does this work for everyone ?


    *

    Offline philmoz

    • *****
    • 2936
      • Photos
  • Publish
    Re: New & orphan ports - what to do and when ?
    « Reply #4 on: 24 / February / 2012, 19:56:20 »
    I'd also suggest adding one or more statuses (e.g. PRE_ALPHA) to help differentiate the state of the port.
    Okay - I'll take a stab at it :

    1) pre-Alpha = code saved for reference, does not compile  -  SKIP_AUTOBUILD
    2) Alpha = code compiles, some functions not implemented or known not to work - SKIP_AUTOBUILD
    3) Beta = code compiles,  all functions implemented, testing needed
    4) Released = code in circulation for at least 4 weeks, all bugs from Beta stage corrected

    Does this work for everyone ?


    Fine with me.

    A quick check shows the following cameras with versions not in SVN:
    - A800 - patch for trunk available; but not yet added to SVN
    - SX210IS - code available; but in an unknown state
    - IXUS115 - work in progress; but code lost due to HD crash (not a lot we can do about this).

    Are there any others?

    Phil.
    CHDK ports:
      sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
      g12 (1.00c, 1.00e, 1.00f & 1.00g)
      sx130is (1.01d & 1.01f)
      ixus310hs (1.00a & 1.01a)
      sx40hs (1.00d, 1.00g & 1.00i)
      g1x (1.00e, 1.00f & 1.00g)

  • Publish
    Re: New & orphan ports - what to do and when ?
    « Reply #5 on: 24 / February / 2012, 21:07:23 »
    A quick check shows the following cameras with versions not in SVN:
    - A800 - patch for trunk available; but not yet added to SVN
    - SX210IS - code available; but in an unknown state
    - IXUS115 - work in progress; but code lost due to HD crash (not a lot we can do about this).

    Are there any others?
    A2100 ?

    http://chdk.setepontos.com/index.php?topic=7433.msg81604#msg81604

    I'm working on a patch file for the SX210 now ....  won't build - multiple problems including needing propset5 .  There is no firmware dump available either apparently.  Guess it gets submitted as pre-Alpha.

    « Last Edit: 24 / February / 2012, 21:41:02 by waterwingz »

  • Publish
    Re: New & orphan ports - what to do and when ?
    « Reply #6 on: 25 / February / 2012, 13:09:38 »
    I'm working on a patch file for the SX210 now ....  won't build - multiple problems including needing propset5 .  There is no firmware dump available either apparently.  Guess it gets submitted as pre-Alpha.
    Got it to build - alpha status patch files submitted for inclusion in the svn at some point.

    *

    Offline msl

    • *****
    • 1177
    • A720 IS, SX220 HS 1.01a
      • CHDK inside
  • Publish
    Re: New & orphan ports - what to do and when ?
    « Reply #7 on: 25 / February / 2012, 15:29:41 »
    Are there any others?

    ixus105 sd1300 - a big porting thread. Maybe microfunguy could help? 8)


    Generally is it a very good idea to collect all started ports.

    msl
    German CHDK pages:  CHDK forum | CHDK inside | CHDK Twitter News by msl | Download CHDK-DE (Autobuild)
    Note: SDM violates the GPL rules!


    *

    Offline srsa_4c

    • ******
    • 3135
  • Publish
    Re: New & orphan ports - what to do and when ?
    « Reply #8 on: 11 / March / 2012, 17:38:42 »
    ixus105 sd1300 - a big porting thread. Maybe microfunguy could help? 8)
    Not until SDM 1.86 gets released  :-X

    S80: http://chdk.setepontos.com/index.php?topic=336.msg82019#msg82019

    My two ports (I'll do these myself if they are needed):
    A420 http://chdk.setepontos.com/index.php?topic=6551.0
    Ixus30/SD200 http://chdk.setepontos.com/index.php?topic=6934.0

    *

    Offline reyalp

    • ******
    • 9957
  • Publish
    Re: New & orphan ports - what to do and when ?
    « Reply #9 on: 11 / March / 2012, 17:42:57 »
    Don't forget what the H stands for.

     

    Related Topics