> Bob wrote: > I have not used the script in a while but is there an entry at the > beginning of the file that looks something like this: > > * ~x86 > > If so, that covers everything with the ~x86 keyword. > > Regards, > > Bob > >
Hi, I wrote in my first post that I'm using stable packages (x86). On my systems with testing packages I have the following entry in the keywords.conf: * x86 ~x86 That's ok,but the keywords.conf is primary also for stable systems to allow packages from testing. I had only reported that the script isn't migrating the package.keywords from Portage correctly.Maybe one reason is that I have a directory package.keywords with files named like categories and put there the entries categorie/package in.This can be handled from Portage since 2.1 or so.This is clearer than one file with dozens of packages in it. One issue I have forgotten to mention: The portage2paludis.bash script adds comments in the file which format is not correct.It creates something like this: ###/etc/portage/package.keywords/media-video begin media-video/tovid media-video/lxdvdrip media-video/streamdvd###/etc/portage/package.keywords/media-video end I don'remember exactly because I edited it manually.But it was something in that form. When Paludis is then searching for packages he says that he can't find package "media-video/streamdvd###/etc/portage/package.keywords/media-video end". The comments have to be seperated by white space or newline.This is another thing the script fails. That's all no big deals but maybe for some newbies a good point to turn away from Paludis. Greetings _______________________________________________ Paludis-user mailing list [email protected] https://lists.berlios.de/mailman/listinfo/paludis-user
