> > > Caution noted. I got caught once lately. On both > 1.4.x and 1.5.0 I keep today's copy, yesterday's > copy and a weekly copy. Since I don't always test > on a regular basis I just added a monthly copy. > It is only a 5 line script in /etc/cron.monthly, > which is a standard feature of Slackware. > > Now I have scrib5, (i.e. today's scribus 1.5.0) > scrib5.bak (yesterday's version) > scrib5.wk and scrib5.mo, all in /usr/local/bin, > and similar copies of scrib4 (scribus 1.4.x) and > inkscape. the odds of scribus 1.5.x going gaga > the night before I create my monthly copy are > about 30 to 1. I think I'll add a scrib5.yr just > in case. There, it's done. > > If some version of Scribus goes belly up linux > users can just drop me a line for a recent clean > copy
Yeah, I?m saying now - it WILL break. Possibly for more than a week at a time. Your scripts will almost surely fail.. Use 1.5.0 that is released. Craig -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 163 bytes Desc: Message signed with OpenPGP using GPGMail URL: <http://lists.scribus.net/pipermail/scribus/attachments/20150311/d82d4a6a/attachment.bin>
