Hi, Am Di., 13. Aug. 2019 um 18:15 Uhr schrieb Derek Atkins <de...@ihtfp.com>: : > > Flatpak builds should follow the same logic as Windows builds. > > Incidentally I like the way that you've separated the flatpack build logs. > > This wasn't me; this was how the build scripts were written. > > > There don't seem to be any flatpak release builds. Should there be and if > > so should I include them in the release downloads on SourceForge and > > Github? > > Not yet. Remember that right now code is sitting behind a tiny straw. > Once I can move back to my main network then we can advertise that.
The other way: At least some should go to a broader download server. This will be important next month for german linux users to get Onlinebanking back, if their distros do not push updates. > I don't know why it's not building the releases. Maybe Geert knows? > > > We only used trac for online code browsing, right? I don't see any reason > > to keep backups of that, all of the actual data are in the repositories. > > I don't think we even use it for that anymore. I don't even have trac > installed. So it's probably safe to delete. (I'll wait for confirmation > before I do). Go! > > So 30G for Windows builds, 24G for Flatpack builds, and 20G for trac > > backups = 74G. What's the remaining 15G? The repos? > > Repos. > Wiki data (and backups) > Email list data & archives > IRC Logs (or possibly something else.. supybot's dir is 4.1G > Then little bits here and there. Good to know. ~Frank _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
