Changes between Version 25 and Version 26 of PortingTips

Timestamp:

08/09/10 21:29:11 (5 years ago)

Author:

michaelvoliveira

Comment:

section titles were resized to fit in the news page

PortingTips

@@ -65 +65 @@
 Also note that doing so may, depending on the project, result in more dependencies but might be easier to handle, for instance when modifying {{{configure.in}}} or {{{Makefile.am}}} instead of an Autoconf-generated {{{configure}}} or Automake-generated {{{Makefile}}}.
 
-== Preparing an archive for distribution ==
+== Preparing for distribution ==
 
 There are two methods for creating an archive for distribution, using DESTDIR and using diff_zip. [[BR]]  
@@ -97 +97 @@
 }}}
 
-== Providing Archive Distributions ==
+== Providing Distributions ==
 
 If the package does not have any of the C++ runtime symbols, then a single package can be created. However if the package is gcc/ABI sensitive, then it should be released as two archives. Ideally one compiled with gcc2 and the other compiled with gcc4. For packages that are only compiled with one gcc, eg gcc4-only software, then a second archive should be created for use with gcc2hybrids.