vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello, does somebody know whether it is "officially supported" to write an ebuild script for a CVS package which requires *several* cvs checkout commands. (Reason: I want to write an ebuild for a package which needs several "internal" libraries which cannot be installed independently but which nevertheless reside in different CVS projects). Of course, I could write the CVS download stuff manually, but this is not what I mean by "officially supported". On the other hand, "inherit cvs" seems in the documented way to provide only *one* cvs checkup/update, or am I missing something? It is currently possible to use internal (undocumented) functions of /usr/portage/eclass/cvs to achieve the goal, but once this file changes, an ebuild using these functions will not run anymore. (As a matter of fact, there is a comment in /usr/portage/eclass/cvs that one should not have any need to use the internal functions). Thanks in advance for any hints. Martin |