Jauhien Piatlicki: > In the ideal country of elves. In the real life it can be not possible to > build and install software in a given distribution without downstream > patches. You can find examples of such live ebuilds in Gentoo tree.
I think it's not appropriate and shouldn't generally be done (with a few exceptions). If the live ebuild needs heavy patching to even work, then don't commit it to the tree. > Anyway, summarizing, it is completely impossible to be sure that live ebuild > will be buildable for you on a given arch in the next 15 min., even if it was > so in the last 15 min. That goes for almost all ebuild variables. So you either drop the whole concept of live ebuilds or you do what is reasonable: a) provide consistent ebuild information, including keywords b) ask upstream about their git workflow, which branches they use, what arches they even officially support c) only add live ebuilds if the upstream git model is something that can be relied upon in one way or another and if you can keep up with the changes If your live ebuild breaks every 15 minutes, then it shouldn't be in the tree. I actually don't commit live ebuild unless I know that upstream is collaborative and I'v contributed to almost all of the projects which I package as live ebuilds.
