Sender:	rich AT delorie DOT com
Message-ID:	<38F22D14.382346D1@bigfoot.com>
Date:	Mon, 10 Apr 2000 20:35:48 +0100
From:	Richard Dawe <richdawe AT bigfoot DOT com>
X-Mailer:	Mozilla 4.51 [en] (X11; I; Linux 2.2.14 i586)
X-Accept-Language:	de,fr
MIME-Version:	1.0
To:	djgpp-workers AT delorie DOT com
CC:	Laurynas Biveinis <lauras AT softhome DOT net>,
	Zippo Workers <zippo-workers AT onelist DOT com>
Subject:	Re: DJGPP library DSMs
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1000410083936 DOT 19649E-100000 AT is>
Reply-To:	djgpp-workers AT delorie DOT com

Hello.

Eli Zaretskii wrote:
> 
> On Sun, 9 Apr 2000, Laurynas Biveinis wrote:
> >
> > Currently only groups can specify which packages do they have. Why do
> > you want it in reverse way?
> 
> The problem with groups being specified on their own DSM files is that
> the group is closed.  How do we add a new package to a group?

You can just create a new version of DSM file. There is a
'dsm-file-version' directive for this purpose.

> For that matter, where will the group DSM be stored?

I imagine that the DSM will be stored on the DJGPP archive somewhere -
wherever appropriate, e.g. in v2gnu for gnutools.dsm. OTOH it may be
better to keep all the DSMs together, perhaps in a directory called
v2packages?

I suspect a solution to this problem may be to create a ZIP file
containing ZIP files for all the packages in the group. Since there is a
distinction between group packages and other packages, this should not be
too hard to add to zippo. e.g. gnutools package contains:

gnutools.dsm
mak3781b.zip
gcc2952b.zip
...

On installing with zippo, the ZIP files would be extracted to a temporary
directory and then the "child" packages would be installed.

Bye,

-- 
Richard Dawe
richdawe AT bigfoot DOT com ICQ 47595498 http://www.bigfoot.com/~richdawe/

- Raw text -