On Thu, Jan 04, 2001 at 11:05:17PM +0100, Goswin Brederlow wrote:
> > On Thu, Jan 04, 2001 at 05:56:37PM +0100, Goswin Brederlow
> > wrote:
> >> >>>>> " " == Dave Dykstra <[EMAIL PROTECTED]> writes:
> >>
> >> Strange, I have % rsync --version rsync version 2.4.6 protocol
> >> version 24 but giving --exclude '*' and
> >> --include-from=.filelist (without directories) works fine. I
> >> don't have any patterns in .filelist though, just actuall files
> >> with full path.
>
(The next quoted text was a private email exchange)
> > What do you mean by works fine? It will copy things without
> > listing the explicit directories? Can you give me a simple
> > example to reproduce it?
>
> > - Dave
> Hmm, its a script that creates a list of all current debian packages
> that are already moved to the pools. The call is:
...
> rsync -rlpt --partial -v --progress \
> ftp.de.debian.org::debian/pool/ \
> --include-from .filelist --exclude '*' pool/
>
> and .filelist contains for example (first few lines of a sorted list):
>
> ./contrib/a/aktion/aktion_2.1-20010101-1.diff.gz
...
I see what you mean: that does copy the files (although I had to manually
create the directories). I note that if you put any wildcard into .filelist
(such as appending a '*' to the above filename) then it doesn't copy
anything. My conclusion is that they're running rsync 2.3.2 or earlier on
ftp.de.debian.org; since you are pulling files, the include/exclude
processing is being done on the server side.
Oh oh, I think that means it will require a slight change to the rsync
protocol to implement --files-from for the pull case. Oh well, that's not
too hard to do.
- Dave Dykstra
