> this. Why don't handle it the "gimp"-way and let someone else provide > the installer for Windows or any other os? One would "just" need a
Because someone else may get it wrong, or never do it, or not document it sufficiently, or not maintain it, or not support it. Data normalization applies to more than just databases. > Some people like all-in-one packages anyway, like WAMP, if SCMBug just > pre-defines some constants for working anything else is not your > business anymore. I disagree. It will be my business when people contact the mailing list for the installer failing. I will have to support it. For example, a Windows installable version not being available when a new Scmbug version becomes available. I might as well embrace it and release a Windows installable version in an automated way. And to reduce the fragmentation of multiple Scmbug installers by multiple people I need to maintain a single installer and support it.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
