Hello,
Just to document this.
I managed to make paludis work as I expect in order to test packages
as I used to do with ebuild command.
It may be not the best solution, but at least it provides one.
The following contents is of /etc/paludis/hooks/stop.bash:
---
stage="$(echo "${HOOK}" | sed -e 's/ebuild//' -e 's/post//' -e 's/_//g')"
[ "${LOCAL_STOP}" = "${stage}" ] && die "Stop requested at ${stage}"
[ "${LOCAL_PAUSE}" = "${stage}" ] && (ewarn "Stop requested at
${stage}, press <Enter>"; read f)
exit 0
---
Then create a link of each post phase you like, for example:
ln -s ../stop.bash /etc/paludis/hooks/ebuild_unpack_post/stop.bash
ln -s ../stop.bash /etc/paludis/hooks/ebuild_compile_post/stop.bash
ln -s ../stop.bash /etc/paludis/hooks/ebuild_install_post/stop.bash
BTW: It would have been easier if the hooks method was also available
for ebuilds, not sure why there is a difference between different
hooks.
The following contents is of /etc/paludis/use.conf.d/inject.bash:
---
[ -n "${LOCAL_USE}" ] && echo "*/* ${LOCAL_USE}"
exit 0
---
Now, one can do:
LOCAL_USE="force" LOCAL_STOP="unpack" paludis --install <package>
Which is similar to:
USE="force" ebuild <package> unpack
I also added LOCAL_PAUSE, to pause between phases.
Still missing in paludis:
1. Simple digest client. Nothing fancy (no changelog etc) only fetch and digest.
2. Cross compile support, contrarius is not working as crossdev and
response I got is that it is unmaintained.
3. Binary packages, Ticket #124 does not provide solution for having
each computer with ability to detach from a network.
Regards,
Alon.
_______________________________________________
paludis-user mailing list
[email protected]
http://lists.pioto.org/mailman/listinfo/paludis-user
