Hello all. First of all, let me say this is for a semi-private project, which I plan to release as soon as possible for testing. The URL in this Bug Report links you with the website of the GoboLinux distribution. At first, it's not that great, I'll admit. But i fell, as we say, in "love" with the filesystem concept. So much that I wanted to revamp the Portage system to take the Gobo FS tree architecture, so that some Gentoo's have a FS tree "OSX-style". Work on the subject is slowly progressing. I am coming closer and closer to a workable portage system, with which i'll surely try making up a stage1 from scratch (viva Qemu). But there are presently some blockings. For example, the mv command is hardcoded in the bash ebuild. but the ln command is wrapped. I know it's ridiculous, but would it be possible to make wrappers for more (and more and ...) commands, simple as they are? Thank you for your time
be more specific ...
I don't think we should make more trivial wrappers for system commands, especially if they only add a $D somewhere. Just more bloat to maintain IMO. Out of curiousity, how would this help you?
well, like in my example, bash uses mv directly. if it uses a hypothetical "domv" always, the ebuild will not have to be "sed"'d or manually modified - I (personnaly) want to make my portage adaptation as smooth as can be done, and this includes not editing the ebuilds in any way. With the number of ebuilds available, it would only be insane to sed through everything. So if there's a domv command used, I won't have to edit all the ebuilds directly calling mv, as they (should be) are using a domv command. That's my vision though. I'll add more details if need be. Would you have another idea?
should i add that in "my" FS tree mod (taken from gobo directly), there shouldn't be "visible" / "accessible" /usr, /bin and such, as they will be almost kernel-hidden? Meaning "i" can't possibly keep ebuilds with hardcoded paths in. And sedding the tree is a killer. (or any automated mod operation)
it would be a lot more sane to add wrappers called 'mv' and such in a special dir and in src_install, setup PATH with that dir in it first that said, i dont think this is worth the effort for portage ...
hm. didn't quite think about that. programmer skills upgraded. thanks, sir. bug changed to invalid.
