[DOCS] Minor changes for FAQ_DEV

2006-10-16 Thread Devrim GUNDUZ

Hello,

I updated RPM related parts in FAQ_DEV against HEAD. It has now more
current information. It will be better if someone checks the wording
before committing.

Please apply.

Regards,

-- 
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/

*** FAQ_DEV.old	2006-10-16 18:29:47.0 +0300
--- FAQ_DEV	2006-10-16 15:26:26.0 +0300
***
*** 1,7 
  
Developer's Frequently Asked Questions (FAQ) for PostgreSQL
 
!Last updated: Wed Sep 6 20:12:13 EDT 2006
 
 Current maintainer: Bruce Momjian ([EMAIL PROTECTED])
 
--- 1,7 
  
Developer's Frequently Asked Questions (FAQ) for PostgreSQL
 
!Last updated: Mon Oct  16 15:24:36 EDT 2006
 
 Current maintainer: Bruce Momjian ([EMAIL PROTECTED])
 
***
*** 386,399 
 
1.14) How are RPMs packaged?

!This was written by Lamar Owen:
 
!2001-05-03
 
 As to how the RPMs are built -- to answer that question sanely
!requires me to know how much experience you have with the whole RPM
 paradigm. 'How is the RPM built?' is a multifaceted question. The
!obvious simple answer is that I maintain:
  1. A set of patches to make certain portions of the source tree
 'behave' in the different environment of the RPMset;
  2. The initscript;
--- 386,399 
 
1.14) How are RPMs packaged?

!This was written by Lamar Owen and Devrim Gündüz:
 
!2006-10-16
 
 As to how the RPMs are built -- to answer that question sanely
!requires us to know how much experience you have with the whole RPM
 paradigm. 'How is the RPM built?' is a multifaceted question. The
!obvious simple answer is that we maintain:
  1. A set of patches to make certain portions of the source tree
 'behave' in the different environment of the RPMset;
  2. The initscript;
***
*** 406,423 
  5. The spec file that throws it all together. This is not a trivial
 undertaking in a package of this size.
 
!I then download and build on as many different canonical distributions
!as I can -- currently I am able to build on Red Hat 6.2, 7.0, and 7.1
!on my personal hardware. Occasionally I receive opportunity from
!certain commercial enterprises such as Great Bridge and PostgreSQL,
!Inc. to build on other distributions.
!
!I test the build by installing the resulting packages and running the
!regression tests. Once the build passes these tests, I upload to the
!postgresql.org ftp server and make a release announcement. I am also
!responsible for maintaining the RPM download area on the ftp site.
!
!You'll notice I said 'canonical' distributions above. That simply
 means that the machine is as stock 'out of the box' as practical --
 that is, everything (except select few programs) on these boxen are
 installed by RPM; only official Red Hat released RPMs are used (except
--- 406,430 
  5. The spec file that throws it all together. This is not a trivial
 undertaking in a package of this size.
 
!PGDG RPM Maintainer builds the SRPM and announces the SRPM to the 
!pgsqlrpms-hackers list. This is a list where package builders are 
!subscribed. Then, the builders download the SRPM and rebuild it on their
!machines. 
! 
!We try to build on as many different canonical distributions as we can. 
!Currently we are able to build on Red Hat Linux 9, RHEL 3 and above, 
!and all Fedora Core Linux releases.
!
!To test the binaries, we install them on our local machines and run
!regression tests. If the package builders uses postgres user to build the
!rpms, then it is possible to run regression tests during RPM builds.
! 
!Once the build passes these tests, the binary RPMs are sent back to PGDG 
!RPM Maintainer and they are pushed to main FTP site, followed by a 
!release announcement to pgsqlrpms-* lists, pgsql-general and 
!pgsql-announce lists.
! 
!You'll notice we said 'canonical' distributions above. That simply
 means that the machine is as stock 'out of the box' as practical --
 that is, everything (except select few programs) on these boxen are
 installed by RPM; only official Red Hat released RPMs are used (except
***
*** 430,484 
 compiler is used -- and only the standard official kernel is used as
 well.
 
!For a time I built on Mandrake for RedHat consumption -- no more.
!Nonstandard RPM building systems are worse than useless. Which is not
!to say that Mandrake is useless! By no means is Mandrake useless --
!unless you are build

Re: [DOCS] Minor changes for FAQ_DEV

2006-10-16 Thread Bruce Momjian

Patch applied.  Thanks.

---


Devrim GUNDUZ wrote:
-- Start of PGP signed section.
> 
> Hello,
> 
> I updated RPM related parts in FAQ_DEV against HEAD. It has now more
> current information. It will be better if someone checks the wording
> before committing.
> 
> Please apply.
> 
> Regards,
> 
> -- 
> The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
> Managed Services, Shared and Dedicated Hosting
> Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
> 

[ Attachment, skipping... ]

[ Attachment, skipping... ]
-- End of PGP section, PGP failed!

-- 
  Bruce Momjian   [EMAIL PROTECTED]
  EnterpriseDBhttp://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---(end of broadcast)---
TIP 6: explain analyze is your friend


Re: [DOCS] Dtrace docs for core docs?

2006-10-16 Thread Josh Berkus
Peter,

> > I'm thinking that some amount of DTrace documentation ought to go
> > into the main docs.  I'm just not sure how much.
>
> I think pretty much all of it.

Ok, will work on formatting it.  I'll try to make it more about DTrace as 
an example of the GMF than anything else.

BTW, is the Dtrace build docs straightened out, or do I still need to patch 
it?  i.e. does it acurrately reflect that you need Solaris 10 update3 or 
OpenSolaris to build, currently?

-- 
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco

---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
   subscribe-nomail command to [EMAIL PROTECTED] so that your
   message can get through to the mailing list cleanly