Subject: Re: crypto-intl "make release" fails
To: None <current-users@netbsd.org>
From: Bernd Ernesti <netbsd@arresum.inka.de>
List: current-users
Date: 03/15/2000 20:17:16
On Tue Mar 14 18:27:51 2000, Hubert Feyrer wrote:
> 
> 
> On 14 Mar 2000, Johan Danielsson wrote:
> > > Ic... do you know what's the state with merging crypto.us and
> > > crypto-into?
> > No. Is this a practical or a political matter? I guess it won't happen
> > before 1.5 anyway.
> 
> Practical, at least for me - see my original message.  Right now it seems
> you cannot generate working snapshots due to broken set-lists. The needed
> files/libs are not tar'ed up.

etc/Makefile needs to be told to get the right set list.

There is one for crypt-intl, but the current Makefile uses only
secr for -us and -intl, and not cryptint for -intl and secr for -us.

Something like this:

*** Makefile	Fri Mar 10 13:54:31 2000
--- Makefile	Wed Mar 15 20:12:40 2000
***************
*** 248,255 ****
--- 248,260 ----
  	sh ../distrib/sets/maketars -s ../distrib/sets \
  		-d ${DESTDIR} -t ${RELEASEDIR}/binary/sets
  .if defined(CRYPTOPATH) && exists(${CRYPTOPATH})
+ .if ${CRYPTOBASE} == "crypto-us"
  	sh ../distrib/sets/maketars -s ../distrib/sets \
  		-d ${DESTDIR} -t ${RELEASEDIR}/binary/security secr
+ .else
+ 	sh ../distrib/sets/maketars -s ../distrib/sets \
+ 		-d ${DESTDIR} -t ${RELEASEDIR}/binary/security cryptint
+ .endif
  	sh ../distrib/sets/makesums -t ${RELEASEDIR}/binary/security
  .endif
  	sh ../distrib/sets/makesums -t ${RELEASEDIR}/binary/sets

Bernd