Richard Marzan <[EMAIL PROTECTED]> writes:
> May i have that script? I assume it's GPLed :-)
Honestly, calling it a script is an embellishment.
Perhaps phrasing it as 'something that keeps the faster moving parts of
configuration in sync' would have been better.
echo '*/* x86' > /etc/paludis/keywords.conf
grep -h -v \# /etc/portage/package.keywords/* | grep \/ | awk -F" " '{print $1
" x86 ~x86"}' | sort -u >> /etc/paludis/keywords.conf
cat /etc/paludis/package_mask.conf | grep -v '::' | grep -v '#' | sort -u >
/etc/portage/package.mask/paludis
cat /etc/paludis/package_unmask.conf | grep -v '::' | grep -v '#' | sort -u >
/etc/portage/package.unmask/paludis
cat /etc/paludis/use.conf | grep -v '::' | grep -v '\*\/\*' | grep -v '#' |
sort -u > /etc/portage/package.use/paludis
That's all there is to it, and it makes a lot of assumptions: that
you've already configured both paludis and portage, that you consider
/etc/paludis authoritative on everything but package.keywords, that
you're running a mixed x86 and ~x86 system, and probably others I can't
spot. You also have to sync the global use flags by hand in make.conf
ans use.conf, as well as manage adding/removing overlays by hand, and it
won't touch CFLAGS settings either, etc.
Another thing to keep in mind is that if you package unmask/mask a
package from a certain repository only with cat/pkg::repo, portage won't
know about it and probably not do what you want.
János Zsitvai
--
[EMAIL PROTECTED] mailing list
