Expense tracking

Forums Submissions Complete Expense tracking

This topic contains 33 replies, has 4 voices, and was last updated by  Michael Totschnig 6 days, 1 hour ago.

Viewing 15 posts - 1 through 15 (of 34 total)
  • Author
    Posts
  • #1866
    #1928

    laga
    Member

    Fails to build from source, unfortunately. https://github.com/mtotschnig/MyExpenses/issues/26

    #1937

    Building MyExpenses requires a modification to the Android SDKs build file. This is documented in MyExpenses build file
    https://github.com/mtotschnig/MyExpenses/blob/master/build.xml
    Is this a problem for including it into f-droid?

    Best regards,

    Michael

    #3477

    CiaranG
    Member

    This is a problem currently, yes. We don’t support building with modified versions of the SDK or NDK, and there are a few apps that require one or the other (the latter is more common). There are plans to support this in the future though.

    #4845

    I have modified the build process, and MyExpenses now builds with the standard SDK build file.

    #4848

    daithib8
    Moderator

    Added. It will be in the repo in a day maybe.

    #4989

    daithib8
    Moderator

    Sorry about the delay. It should be there soon.

    #5189

    Thanks this is good news.

    Now, I have one question. I see on http://gitorious.org/f-droid/fdroiddata/blobs/master/metadata/org.totschnig.myexpenses.txt that auto update mode is none. What do I need to do to make updates automatic?

    I am currently tagging all releases published with Google play (last one is r33). Additionnally, I would like to make alpha releases available through F-Droid, if they are clearly marked as such in the f-droid interface.

     

    #5192

    daithib8
    Moderator

    If you want to use alpha releases, we would need to change Update Check Mode to none and set the current version manually. Then , you can post the commit etc here, or do a merge request on gitorious.org. Otherwise auto update is possible but risky as , if something breaks, our build server doesnt give us much feedback.

    #5193

    I can submit merge requests through gitorious. But how do you recognize the difference between alpha and stable releases and how are they displayed in f-droid client? Thanks.

    #5194

    daithib8
    Moderator

    The F-droid client puts an asterisk next to one build, that whose version code is equal to or closest to the Current Version Code as taken from the metadata. The Current Version Code can be automatically updated or manually updated, depending on the app.

    #5195

    Sorry, I still have difficulty understanding the workflow. Currently, my stable release is published and visible in the metdata
    Current Version:1.5.1
    Current Version Code:33

    When I make a new stable release, I submit a merge request to have the new current version appear in the metadata.

    But if I want to make pre-release version 1.6.0a1 available through F-droid, how do I proceed? Announce it here in this thread, and you will pick it up from Github?

    #5196

    daithib8
    Moderator

    You provide a Build Version line for 1.6.0a1 but you leave the Current Version (Code) unchanged. That way people won’t be prompted to update. The Current Version is only updated for stable releases which can be done automatically by checking for new tags. You can provide Build Version lines or Current Version changes via git or via the forum.

    #5310

    As discussed, I’d like to make the following beta release available through F-Droid:
    Build Version:1.6.0b1,34,695df8d438896be3733da45ff80d86524da0c4bd,prebuild=rm -rf tests

    Thanks,
    Michael

    #5311

    daithib8
    Moderator

    We have a number of apps in the queue that havent been built: same reason as the delay for the original submission. It should be sorted within a week I think

Viewing 15 posts - 1 through 15 (of 34 total)

You must be logged in to reply to this topic.