Bug 17903 - Allow CVS_UPDATE to be used with SUP_UPDATE w/o PORTSSUPFILE
Summary: Allow CVS_UPDATE to be used with SUP_UPDATE w/o PORTSSUPFILE
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: bill fumerola
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-04-10 15:30 UTC by James Housley
Modified: 2000-10-31 21:00 UTC (History)
0 users

See Also:


Attachments
file.diff (921 bytes, patch)
2000-04-10 15:30 UTC, James Housley
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description James Housley 2000-04-10 15:30:02 UTC
	The src/Makefile allows update to use both SUP_UPDATE and CVS_UPDATE
	at the same time, ie.  SUP to update the secure & crypto tree and 
	CVS to update from the local cvs tree.

	ports/Makefile won't use CVS_UPDATE if SUP_UPDATE is defined.  Not
	only that but there is an error because PORTSSUPFILE is not defined.

	The attached patch:
	  Uses SUP if SUP_UPDATE & PORTSSUPFILE are both defined
	  else uses CVS_UPDATE if defined
	  else produces an error (like before) if SUP_UPDATE is defined
	    but PORTSSUPFILE is not defined
	  else produces and error SUP_UPDATE or CVS_UPDATE must be defined
Comment 1 bill fumerola freebsd_committer freebsd_triage 2000-04-10 18:17:36 UTC
Responsible Changed
From-To: freebsd-ports->billf

I added PORTSSUPFILE and the makefile logic, I'll look at this. 

Comment 2 jeh freebsd_committer freebsd_triage 2000-10-02 18:43:18 UTC
I am not sure if this is still needed or not since the crypto parts are
available via CTM.

Jim
-- 
Do not meddle in the affairs of dragons, for you are crunchy and taste
    good with ketchup.
Comment 3 jeh freebsd_committer freebsd_triage 2000-10-31 21:00:07 UTC
State Changed
From-To: open->closed

Committed.