On 01/27/2018 03:30 AM, Michał Górny wrote: >> >> What are we worried about in using a temporary directory? Copying across >> filesystem boundaries? Except in rare cases, $DISTDIR itself will be >> usable a temporary location (on the same filesystem), won't it? > > Why add the extra complexity when there's no need for one? Note that > there's also the problem of resuming transfers, so in the end we're > talking about permanent temporary directory where we keep unfinished > transfers.
Can't argue with that, but I don't see it as a huge "con." >> For the second point, portage is going to tell me where to put the file, >> isn't it? Then no matter what garbage I download, won't portage look for >> it in the right place, because where-to-put-it is determined using the >> same manifest hash that determines where-to-find-it? > > No, it won't. Why would it? You're going to call something like: > > edistadd foo.tar.gz bar.tar.gz > > ...and it will place the files in the right subdirectories. If we have a tool like edistadd, then I see the problem. But if we were going to use file-data based hashes, then there would be no need for a tool in most cases. As a developer, "repoman manifest" would handle it. As a user, I'm going to see a message like, Fetch instructions for games-fps/doom3-lms-4: * Please download LastManStandingCoop4Multiplatform.zip from: * http://www.moddb.com/mods/last-man-standing-coop/downloads * and move it to /var/cache/portage/distfiles except instead of $DISTDIR, it would suggest whatever directory is computed from the hash in the manifest.
