Summary: | Make more wrappers for simple operations. | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Renaud Lepage <rlepage> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | rlepage |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.gobolinux.org/ | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Renaud Lepage
2005-05-04 18:12:52 UTC
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. |