Bug 11335 – repoman checks PORTDIR_OVERLAY, undesired

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Zach Welch (RETIRED) 2002-11-28 07:09:30 UTC]

I have my local portage tree over nfs, and i noticed repoman was scouring it  
when run from the root of the portage tree.  strace verifies this is the case. 
  
Using `PORTDIR_OVERLAY="" repoman full` solves it for one shot, but the 
current behavior is a 'bug', in my view.  Multiple portdir overlays would 
make this even more problematic. 
  
I'd like to help with this, but I need pointers into the codebase.  A little  
handholding, if you will.  
 
occurs in portage 2.0.44

[Comment 1 SpanKY 2003-01-08 14:17:15 UTC]

i believe a cmdline option would be better ... people may want PORTDIR_OVERLAY
checked (i would :D)

[Comment 2 Zach Welch (RETIRED) 2003-01-11 21:13:02 UTC]

but repoman is meant for scanning the checked out CVS tree just prior to
a commit, so it doesn't make sense (to me) to scan anything except
this core tree.  Everything scanned is destined (soon) for the main tree.
If anything, I would propose your suggested command-line option *re-enable* 
the present functionality, otherwise disabled by default.

Is your /usr/portage tree an rsync copy and your PORTDIR_OVERLAY your cvs tree?
If that's the case, I can see your argument clearly, but would that even work?
That seems scary since portage still doesn't tell where exactly it got its
ebuild - you can't tell if it's using one from your overlay or the core tree.

[Comment 3 SpanKY 2003-01-12 11:41:42 UTC]

actually i maintain 3 trees ;) 
/usr/portage is rsync 
/usr/local/portage is where i tool around 
/usr/local/gentoo-x86 is cvs 
 
keeps things cleaner that way imo 

[Comment 4 Zach Welch (RETIRED) 2003-01-13 13:23:11 UTC]

so you're using multiple overlays?  if so, i'd suggest that remoman needs
a feature listing which trees it should scan. (printing them as part of its
verbose report).  alternatively, a list of trees *not* to scan. whatever. :)

but multiple overlays aren't in mainstream portage, right? so this is
all very premature for repoman... ;)

[Comment 5 Marius Mauch (RETIRED) 2003-10-09 12:31:09 UTC]

re-assigning to puggy as he is the main repoman guy now. 

[Comment 6 Marius Mauch (RETIRED) 2003-11-15 17:08:38 UTC]

*** Bug 33543 has been marked as a duplicate of this bug. ***

[Comment 7 Masatomo Nakano (RETIRED) 2004-03-06 00:14:03 UTC]

Fixed in CVS.

[Comment 8 Torsten Veller (RETIRED) 2004-07-04 09:49:15 UTC]

...another irritating behaviour: more than one entry in PORTDIR_OVERLAY is not supported by repoman (Portage 2.0.51_pre12):

>1:

# egrep ^PORTDIR_OVERLAY /etc/make.conf
PORTDIR_OVERLAY="/usr/portage/local1 /usr/portage/local2"

(fyi PORTDIR="/usr/portage/portage")

# pwd
/usr/portage/local1/app-doc/howto-html
# repoman
repoman: We do not appear to be inside a local repository or a portage tree. Exiting.

=1:

# egrep ^PORTDIR_OVERLAY /etc/make.conf
PORTDIR_OVERLAY="/usr/portage/local1"
# repoman
not in a CVS repository, enabling pretend mode
We're not in PORTDIR... unable to determine a PORTDIR.
RepoMan pretends to scour the neighborhood...

[Comment 9 Jason Stubbs (RETIRED) 2004-10-04 06:41:12 UTC]

Second bug fixed. Closing so it's not forgotten about.