Am Mittwoch, 7. Februar 2007 19:10 schrieb Waldemar Brodkorb: > Hi, > > On Wed, 07 Feb 2007 at 17:25 +0100, Ralph Passgang wrote: > > I am now finally happy with the state of shorewall (as long as no bug > > will be discovered) and will not touch the trunk version anymore. You > > told me privately, that you want to include the latest release candidate > > in trunk, so please go ahead. :) > > Only in special cases we should use release candidates or cvs/svn > checkouts. You can always add new features via patches and remove > them as soon as upstream has a release. > > But why the hell is shorewall package so important, we have more > then 300 ppackages. Can you take care of other packages as > well in the same intensive way? :p
I updated bind, rsync and nano last week (altogether this fixes a security issue as well as a dirty segfault bug and rsync 2.6.9 should also be better (and more stable) then 2.6.8) and trying to understand why my new package scsi-spin fails (maybe really the kernel patch is missing) at the moment. As you know I do quite a lot other things too, so I cannot upgrade 30 packages a week and that every week. In this week, for example, there will be definitly less time for contributing to freewrt than last week. That will change from week to week. It's not that shorewall took so much time, maybe it's even the other way around. I used to less time for it, that's why so many commits became nessessary. The total amount of commits doesn't neccessarly reflect the amount of time that somebody spent on a subject. But as I said, I am now quite happy about the package and the only thing that I will do before not touching it anymore is to merge the last changes from today to the branch version. So, if nothing bad happens, it's just one more commit and you will not have to read all the commit messages any further. But maybe you just need a filter for your commit mails.... something like "IF mail.body INCLUDES "shorewall" THEN MOVETOFOLDER .SPAM/" ;-P --Ralph > bye > Waldemar _______________________________________________ freewrt-developers mailing list [email protected] https://www.freewrt.org/lists/listinfo/freewrt-developers
