01:39:05 < Ch00k> hi everybody
01:39:50 < Ch00k> I need to consult someone regarding the situation I have when updating from 5.8.8 to 5.12.2
01:40:07 < Ch00k> http://pastebin.com/g62DAmvc
01:40:38 < Ch00k> it seems that the ebuild should create the vendor_perl directory, but it doesn't
02:01:22 < kent\n> * Generating ConfigLocal.pm (ignore any error) ...
02:01:53 < kent\n> its probably because the vendor dir is not created until *after* installing perl.
02:02:05 < kent\n> Ch00k: Check your filesystem, I bet its there.
02:02:40 < Ch00k> I checked, there is no vendor_perl in the whole /
02:03:02 < kent\n> qlist dev-lang/perl | grep -i vendor 
02:03:51 < kent\n> oh, wait, its possibly not there because its empty. duh. Its probably created by the first module to be installed then
02:04:46 < kent\n> I guess we *could* make this forced creation by putting a .keep file in there ? tove ?
02:04:55 < kent\n> but I don't see the point 
02:05:12 < kent\n> vendor_perl is for stuff from modules
02:05:22 < kent\n> Ch00k: what do you need it for, that is the question
02:05:33 < Ch00k> does the module ebuild create that dir?
02:05:48 < kent\n> Ch00k: I think its "portage" that creates it
02:05:50 < Ch00k> I don't need it, I just wanted to know if it's not a bug
02:06:15 < kent\n> last I checked no packages "own" a given directory, they just tell portage "I need a file in $directory" and portage makes sure its there if its not 
02:06:21 < kent\n> and portage gets rid of it again when its empty 
02:07:35 < kent\n> Ch00k: try installing/reinstalling a dev-perl/ module, I expect it will put stuff in vendor_perl and that directory will automatically come into existance, regardless of which module you choose
02:08:50 < kent\n> List-MoreUtils should be a good one, no deps.
02:09:03 < Ch00k> ok, I'll try, thanks
02:12:39 < Ch00k> though, maybe it could be more user-friendly to create the dir on perl emerge?
02:12:51 < Ch00k> to get rid of these errors
02:14:06 < kent\n> Yah. It wouldn't get rid of those errors I think, but it would perhaps make things more obvious =)
02:14:58 < kent\n> unless we create /usr/lib64/perl5/vendor_perl/5.12.2/x86_64-linux  also 
02:16:09 < kent\n> /usr/lib64/perl5/vendor_perl/5.12.2/x86_64-linux/.keep  # would probably do 99% of the problem 
02:16:24 < Ch00k> well, can't you let those two dirs be created upon perl emerge?
02:17:18 < kent\n> I don't think you can "Create dirs" in the way portage thinks, I'm not sure though, but you *can* create files and portage makes sure their dirs exit 
02:17:19 < kent\n> exist* 
02:17:40 < Ch00k> that's what I meant :)