I'm building my new stuff against svn head. You can build against whatever you think is stable right now. If you have a working binary, I would just drop it in place right now, and then update it when you have a stable new release.

On 01/25/2013 05:23 PM, Greg Hellings wrote:



On Fri, Jan 25, 2013 at 5:42 AM, Troy A. Griffitts <scr...@crosswire.org <mailto:scr...@crosswire.org>> wrote:

    Dear Frontend Teams,

    I'm planning to burn CDs for people (about 60) who have requested
    them (yes, we still get occasional CD requests), and was wondering
    if you might wish to update your stuff in the 'latest' ISO folder
    here which is the root from where we build the ISO.

    ftp://ftp.crosswire.org/pub/sword/iso/latest/

    I'll update the modules and clean off the ridiculously archaic
    blobs of whatever.


Is your intention for this CD to include software based off of 1.6.2 or will 1.7 be finished before that for front-ends to target?

--Greg


    Historically, we've tried to include installers for Mac, Windows,
    and Linux.  I'm conceding to give up on the Linux software (on the
    CD), so we should probably just remove all of our Linux binary
    bundles.

    These installers should be configured to allow installing of
    modules from the CD.  The InstallMgr class supports installation
    not just from a remote source, but from a local path as well.  If
    your installers could add the root of the CD path as an install
    source, that would be excellent.

    We also try to make things run from the CD if possible.  I know
    BPBible has a 'portable' install for this and some of our other
    frontends run find from the CD as well.  If there is a binary you
    can place somewhere on the CD that, when double clicked, it can
    start and find it's modules from the CD (at least), that would be
    great.  SWORD looks in the current folder for modules, so if you
    place your binary in the root of the CD, it might just magically
    work.  Otherwise, you could have a subdirectory with your stuff
    and include a sword.conf which specifies a datapath of ../ or
    something.  Just ideas.

    You can download the latest ISO image from here so you can locally
    update it and play to test how your stuff works.

    ftp://ftp.crosswire.org/pub/sword/iso/

    When you get it working well, if you could update the
    crosswire.org:/home/sword/ftp/pub/sword/iso/latest/ with your
    stuff, that would be great.  I'm also happy to update the CD
    autorun splash screens with anything you'd like.  Not sure how
    this works on a Mac, but we launch a silly little windows app with
    buttons to launch each installer.

    We could also think about instructions to help people burn this to
    a thumb drive.

    Thanks for any help,

    Troy



    _______________________________________________
    sword-devel mailing list: sword-devel@crosswire.org
    <mailto:sword-devel@crosswire.org>
    http://www.crosswire.org/mailman/listinfo/sword-devel
    Instructions to unsubscribe/change your settings at above page




_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Reply via email to