ncftp bug (was Re: debian updates tree structure)
Ryan Shaw <ryans@rio.com> typed:
>
[snip]
>
> i then went back to caldera to grab the 1.2.1 release thinking that it
> would be mostly links back to the 1.2 release (other than the updated
> packages).
>
> however, all i got was a bunch of links.
>
> here's how i have my tree setup:
>
[pretty tree output snipped]
>
> i downloaded everything under `rex-fixed' aka Debian-1.2.1 and ended up
> with a bunch of symlinks.
>
> i am using ncftp to grab these.
>
> what am i doing wrong? (besides not ordering a cd)
>
Its not really what you are doing wrong it is what (IMO) ncftp is doing wrong.
I've noticed that ncftp will *not* follow symlinks in at least the case
of get -CR directory_name. I feel that whilst this may be useful behaviour in
some circumstances, that the ommission of an option to turn this "feature" off
is probably a bug. It certainly makes ncftp useless for situations such as
the sensible symlink setup of the 1.2.1 tree. I've meant to send a mail to
the upstream maintainer about this. On this same topic, ncftp with get -CR
will happily merge two files into one if you are doing simultaenous recursive
regets on the same directory. For example get -CR dir1 executed in two
seperate ncftp sessions on the same dir1 will for say the file dir1/filename
create a dir1/filename on your host which is a blend of the two identical
filenames. methinks this is also an avoidable problem (i.e. bug).
>
>
> --
> TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
> debian-user-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com
>
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com
Reply to: