From owner-freebsd-ports  Sat Jun  3 18:05:43 1995
Return-Path: ports-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id SAA23726
          for ports-outgoing; Sat, 3 Jun 1995 18:05:43 -0700
Received: from westhill.cdrom.com (westhill.cdrom.com [192.216.223.57])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA23710
          ; Sat, 3 Jun 1995 18:05:41 -0700
Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1])
          by westhill.cdrom.com (8.6.11/8.6.11) with SMTP id SAA00594
          ; Sat, 3 Jun 1995 18:05:39 -0700
X-Authentication-Warning: westhill.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol
To: asami@CS.Berkeley.EDU (Satoshi Asami)
cc: jkh@freefall.cdrom.com, ports@freefall.cdrom.com
Subject: Re: Change in the package hierarchy organization requested 
In-reply-to: Your message of "Sat, 03 Jun 1995 17:49:54 PDT."
             <199506040049.RAA00769@silvia.HIP.Berkeley.EDU> 
Date: Sat, 03 Jun 1995 18:05:39 -0700
Message-ID: <593.802227939@westhill.cdrom.com>
From: Gary Palmer <gpalmer@westhill.cdrom.com>
Sender: ports-owner@FreeBSD.org
Precedence: bulk

In message <199506040049.RAA00769@silvia.HIP.Berkeley.EDU>, Satoshi Asami write
s:
>That's an interesting problem...that RockRidge thing (I assume it's a
>CDROM burner?) does the same to all the directory names that start
>with ``.''?  If so, I think you need to get that fixed, regardless of
>the package situation.... :<

Nope - it's the mkisofs program which generates an ISO 9660 Level 1
format disk from a UFS filesystem. The problem is ... level 1 is
basically DOS format (with RR extensions), and DOS can't hack dir's
which start with `.' AFAIK.  So the software isn't broken in that
respect, although how it handles the situation most definately IS :-(

>The idea was to put the packages in a hidden directory, or at least
>something that looks significantly different from the others so that
>users can easily distinguish the directories that are safe to "get
><dir>.tar.gz" with those that aren't.

Err. If you get <dir>.tar.gz you'll most probably get a symlink tree
anyhow (haven't tried it, but I'd be surprised if tar followed the
symlinks). I think the solution is to use `all' properly - i.e. put
the real packages into all and symlink into there.

>P.S. Don't tell me RockRidge collapses all names to lowercase. ;)

OK  I won't, but think about DOS naming conventions... :-)

Gary