-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mar 25, 2009, at 9:02 AM, Tarek Ziadé wrote: > Yes but this means that you have to wait for the next version of the > "big" package > when a bug is corrected or a feature added, or you need to patch it. > (or maybe use the namespace trick to override it) > > Having them as separated package allow different release cycles, > which makes it > more "agile". > > I think there should be a right middle between a big package and a > myriad of > small ones. > > In Zope for instance, we could probably reunite a lot of package in > a single > package, because they don't evolve much anymore. (things like > zope.interface) Maybe there's a difference between being a Zope user and using zope packages? I think it's great that I can pick and choose zope.interfaces and other packages in my not-Zope project. But if I'm deploying actual Zope-the-web-thing I just want to install it from my distro and be done with it. It's up to my distro to determine compatibility, handle bug and security fixing, etc. Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBScpFj3EjvBPtnXfVAQJakwP/djOrhpyZZrrqCFNG7rAi3qpZIaVLXiwk U/td3R6OyugcDrnf26+xpaWGjr5HiJsftusRdVPbZmR9kFNmOc15lmJ1b3QElpv5 dofRiQ8hMXqe+sgCm9QmRj5RyszNlALdbYKkjCMODrcKqzC1N6fPjNi03FloWKmd N89NYb75CUo= =dmRY -----END PGP SIGNATURE-----
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4