[GNC-dev] [MAINT] Cleaning up Code (the server)
jralls at ceridwen.us
Tue Aug 13 16:53:34 EDT 2019
> On Aug 13, 2019, at 9:14 AM, Derek Atkins <derek at ihtfp.com> wrote:
> On Tue, August 13, 2019 12:03 pm, John Ralls wrote:
>> Yay! I've been asking for you to clean up the old Windows builds for
>> years! Now for a little preventive medicine: take a few minutes to add a
>> cron job.
> eTooLazy. ;)
> Writing and testing the script would take more time than just going and
> pruning every year or two.
Nah, it's easy: find /home/builder/builds/win32/maint -ctime +180 -delete`.
>> The logs directory could also stand some vacuuming, we really don't need
>> to keep the logs around for more than a few months and they currently go
>> back to the beginning of 2018.
> The logs don't take up much space, but I pruned out the 2018 logs.
>> If you want you could be more aggressive. We don't need to keep release
>> builds at all, they're already all on SourceForge and the newer ones are
>> on Github as well. If you want to keep a separate backup you could keep
>> them somewhere offline. Maint and master builds are of marginal utility
>> after the release they lead up to and it gets more marginal with every
>> subsequent release. 6 months worth (two regular releases) seems about
>> 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.
Ah, duh. So I can fix that in the Windows build script.
>> 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
> 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.
This wouldn't be advertising, it would be me downloading one flatpack at release and uploading it to SF and Github just as I do with Windows releases.
More information about the gnucash-devel