Maybe I am wrong, but a <fileset> or a <filelist> is essentially a
collection of data files with names (isn't logically <filelist> an ordered
<fileset>?). There is no reason for the names to be exactly as they are in
the file system. Some special tasks like <delete> need to access original
files. Some other tasks like <copy> or <zip> need only data from the files.
They do not really care about original file names.

Right now tasks have to be aware about any extra fileset functionality they
support (<zipfileset>, <tarfileset>,...). So the proposal is to make it
generic. One of the beneficiaries is <sync> task. Its main goal is to create
final images, but it is not really useful, since right now it is impossible
to create an image with one command. So maybe instead of fixing each and
every task, it is better to provide a generic solution that covers <copy>,
<zip>, <sync> and others.

- Alexey.

--
{ http://trelony.cjb.net/ } Alexey N. Solofnenko
Pleasant Hill, CA (GMT-8 usually)


-----Original Message-----
From: Stefan Bodewig [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, July 29, 2003 8:46 AM
To: [EMAIL PROTECTED]
Subject: Re: Any chance for fileset arithmetic?

On Tue, 29 Jul 2003, Alexey Solofnenko <[EMAIL PROTECTED]> wrote:
> I think it is easy. <zip> already supports part of it with
> <zipfileset>.

Sure, but not for "plain" filesets.

> <delete> will delete the original file.

I.e. treat it like any fileset.

> <copy> and others will copy or see the files with new names.

I.e. <copy> has to be aware that this is not a "plain" fileset and do
something special with it.

The point I'm trying to make is that the meaning of the prefix
attribute depends on the task - and that the task must be made aware
of it to give it any meaning.

In CVS HEAD, you can define <zipfileset> outside of any tasks and you
can use <zipfileset> wherever you can use a <fileset> in Ant 1.5.  It
sounds as if you really wanted that <copy> and a couple of other tasks
become aware of the fact that they are using a <zipfileset>.

> I just want to avoid copying a hundreds megabytes of data just to
> lay them out correctly.

I completely understand that goal, just think you are tackling it from
the wrong end.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to