mirror of
https://github.com/postgres/postgres.git
synced 2025-06-14 18:42:34 +03:00
Update FAQ_DEV.
This commit is contained in:
@ -545,7 +545,8 @@
|
||||
|
||||
<H3><A name="15">15</A>) How are RPM's packaged?</H3>
|
||||
|
||||
<P>This is from Lamar Owen:</P>
|
||||
<P>This was written by Lamar Owen:</P>
|
||||
<P>
|
||||
<PRE>
|
||||
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.
|
||||
@ -634,10 +635,11 @@ stance. IMHO, of course.
|
||||
Of course, there are many projects that DO include all the files
|
||||
necessary to build RPMs from their Official Tarball (TM).
|
||||
</PRE>
|
||||
<P>
|
||||
|
||||
<H3><A name="16">16</A>) How are CVS branches managed?</H3>
|
||||
<P>This was written by Tom Lane:
|
||||
|
||||
<P>
|
||||
<PRE>
|
||||
If you just do basic "cvs checkout", "cvs update", "cvs commit", then
|
||||
you'll always be dealing with the HEAD version of the files in CVS.
|
||||
|
Reference in New Issue
Block a user