[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Single Page
Top Document: Unix - Frequently Asked Questions (7/7) [Frequent posting]
Previous Document: RCS vs SCCS: How do they handle problems?
Next Document: RCS vs SCCS: Conversion.
-
Search the FAQ Archives
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Single Page
Top Document: Unix - Frequently Asked Questions (7/7) [Frequent posting]
Previous Document: RCS vs SCCS: How do they handle problems?
Next Document: RCS vs SCCS: Conversion.
RCS vs SCCS: How do they interact with make(1)?
>From: Blair P. Houghton <bhoughto@sedona.intel.com> 7.9) RCS vs SCCS: How do they interact with make(1)? The fact that SCCS uses prefixes (s.file.c) means that make(1) can't treat them in an ordinary manner, and special rules (involving '~' characters) must be used in order for make(1) to work with SCCS; even so, make(1) on some UNIX platforms will not apply default rules to files that are being managed with SCCS. The suffix notation (file.c,v) for RCS means that ordinary suffix-rules can be used in all implementations of make(1), even if the implementation isn't designed to handle RCS files specially.
Top Document: Unix - Frequently Asked Questions (7/7) [Frequent posting]
Previous Document: RCS vs SCCS: How do they handle problems?
Next Document: RCS vs SCCS: Conversion.
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Single Page
[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
Send corrections/additions to the FAQ Maintainer:
tmatimar@isgtec.com (Ted Timar)
Last Update October 12 2008 @ 00:13 AM