Summary: | Distfiles overlay directory ($DISTDIR_OVERLAY) | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Alexander Asanov <bobr.x3> |
Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 216231 |
Description
Alexander Asanov
2004-10-25 01:00:26 UTC
man 5 portage Find the part on /etc/portage/mirrors and try the "local" option. Although not yet documented, file system paths are also supported for "local" mirrors. That's not a solution of my problem. It's not even close. My mirror is not in my local network. I want to be able to synchronize with a mirror eventyally with my HDD and then go home with it (mirror in a pocket :). I want to give my HDD to my friends so they could synchronize their distfiles with mine. And I want distfiles to be clean of outdated versions of packages. But I dont want my manually managed distfiles to be affected. That's what I want. To have distfiles from gentoo mirror and not only. And distfiles from mirror should not interfer with other. OK. I reread your message more carefully and I agree, that's a solution of my problem. But I still think, that making $DISTDIR_OVERLAY option in make.conf would be much better way to do sych a thing. It would be a way for people who even don't have such a problem to separate gentoo hosted distfiles from others. And it would be more intuitive. BTW. The feature you described doesn't work. I added "local /usr/local/distfiles" to my /etc/portage/mirrors but portage still can't find my distfiles. fyi, Jason: I have seen a larger thread in the german section of forums.g.o regarding this issue. It was more or less about a workaround for users without a fast internet connection. To be able to moun a cd/dvd with tarballs, having both distfile locations acessible at the same time without the need to copy all of the tarballs to the hdd, would be appreciated as it seems. localhost portage # ls /usr/portage/distfiles/portage-2.0.51-r2.tar.bz2 /home/distfiles/portage-2.0.51-r2.tar.bz2 ls: /home/distfiles/portage-2.0.51-r2.tar.bz2: No such file or directory /usr/portage/distfiles/portage-2.0.51-r2.tar.bz2 localhost portage # cat /etc/portage/mirrors local /usr/portage/distfiles/ localhost portage # emerge info | grep DISTDIR DISTDIR="/home/distfiles" localhost portage # emerge -f portage Calculating dependencies ...done! >>> emerge (1 of 1) sys-apps/portage-2.0.51-r2 to / Local mirror has file: portage-2.0.51-r2.tar.bz2 >>> Previously fetched file: portage-2.0.51-r2.tar.bz2 size ;-) >>> Previously fetched file: portage-2.0.51-r2.tar.bz2 MD5 ;-) >>> md5 src_uri ;-) portage-2.0.51-r2.tar.bz2 Seems to work fine here... Will leave this open for the time being unless somebody else disagrees... DISTDIR=/dir and "local" cover all permutations that we are aware of. I move to punt. Oh, right. I never needed it and wasn't aware that local paths are accepted in /etc/portage/mirrors, too. Oh. No. You offer me to download files from my HDD to my HDD. I should have two copys of the same file. That's not a solution. Dostfiles overlay dir and local distfiles mirror are different features. Both are needed. First to be done, second to be documented. I think this if not very hard. I'll reopen this bug. It's intelligent enough to not copy the files. distfiles overlay directory is needed, i.e. if you run a git-overlay with distfiles in it, i.e. unreleased patches. Please reopen this bug and add the FEATURE. In >=portage-2.1.5 there's a new variable called PORTAGE_RO_DISTDIRS. See `man make.conf`. Maybe that works for you? Seems to be fixed in portage >=portage-2.2_rc1 with PORTAGE_RO_DISTDIRS. Please change state to FIXED. Thanks, reopening to mark fixed... |