Dirk Reiners wrote: > Marcus Lindblom wrote: > > The repository path should definitely be available. It's very useful to > > disambiguate releases etc. > > > > As I showed earlier, we use all available info (version number, revision > > number, path, modified flag) in our releases. > > Modified is a bit of a problem, as it doesn't really help on a > lib-by-lib basis (and not really at all, IMHO). I print a warning when > it finds a modified file, I'd consider that a bug. But the path is needed. > I like that flag for the simple reason that I can be sure that I can check out the exact source that was used to build the binary. If it says '(modified)', all bets are off. :) .. And I like the warning and all that, so that you can do modified dists, but it's dangerous if those modified builds are being let out in the open.
Well, I suppose it's more of an issue with software that has more frequent releases and less picky/careful/experienced people building said releases. :) Cheers, /Marcus ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
