On Mon, 23 Jun 2003, Bruce Momjian wrote: > Peter Eisentraut wrote: > > Bruce Momjian writes: > > > > > Well, it is a nice test template for people who aren't shell script > > > experts, and I have been in the habit of pushing stuff I use into /tools > > > so it is available for others. > > > > I know and I'm not happy about it. The PostgreSQL source tree isn't a > > repository of everyone's favorite shell scripts. There's an official > > method to build and test a PostgreSQL installation. If that is flawed or > > incomplete, then let's talk about it. But everyone pushing out their own > > little test methodology without further consideration is not going to help > > this discussion. > > I put stuff in /tools so if something happens to me, you guys can keep > going. Do I have to be clearer that that? I have RELEASE_CHANGES, > which Tom used for 7.3.X releases, pgindent, stuff for finding > missing/extraneous includes, static requirements, stuff like that. > > Unless you can find someone else who agrees with you, it stays.
Peter is coming off awfully paternalistic here. I'd rather have a few extra scripts to look through to find what I need when I'm trying to figure out something than to have a tool that only the hackers know exists and I can only get by asking nicely to see the pretty code. While no one wants to see a contrib or tool directory of a hundred megs, lots of little example files and testing scripts can be nice for nothing else other than the examples they provide. I learned a lot when I first started using pgsql from the things in the contrib directory. ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
