Subject: Re: Dealing with "secret" subdirectories on the MASTER_SITE
To: Todd Vierling <>
From: Chris Jones <>
List: tech-pkg
Date: 08/06/1998 19:48:13
On Thu, 6 Aug 1998, Todd Vierling wrote:

> On Thu, 6 Aug 1998, Alan Barrett wrote:
> : > * It should probably use libtool.  I'm not familiar with libtool, so I
> : >   didn't do that myself.
> I am in the USA, so I should be able to look into it and libtoolize it.  I
> didn't see the original post - can you send me the location of the pkg?

> I plan on making the docs for libtool much easier to understand.  Explaining
> it to Tim Rightnour cleared it all up in my own head, and I think we both
> fully understand it now.  :>

Wonderful.  I've been thinking I should learn more about libtool, but I
haven't had time to get to it yet.  Are you going to post a pointer to the
docs when you're done with them?

> : > * I couldn't find any simple method of having make automatically
> : >   retrieve the distribution files.  I had to get those by hand.
> : 
> : The Makefile in NetBSD's security/rsaref package has a special
> : "do-fetch" rule to deal with the "secret" subdirectory.
> This is the kind of method that really should be used.  Make note of the
> blank "fetch-list" rule - this is very important, as the rule _must_
> succeed, but you can't give any useful information in a case like this.
> : Would it make sense to put that logic into
> No.  There's way too many ways of having this information hidden on a site.
> (Think HTTP forms.  ;)  It's easier just to let each pkg deal with it.

In fact, krb5 seems to have changed to a form-based interface from the one
I seem to recall.  Ick.

However, there probably is a lot of overlap between different packages.
It wouldn't be surprising for the majority of "secret" packages to hide
themselves in very similar ways.  We might not be able to handle every
case, but maybe we could make things easier for *most* cases.  Just a

Chris Jones                                
           Mad scientist at large          
"Is this going to be a stand-up programming session, sir, or another bug hunt?"