Rene,
I am not sure if you have noticed; but there are many packages in trunk wouldn't build b/c their dependency priorities are just wrong. Managing dependency priority order, i can imagine, is a nightmare unless you have some kind of special tools. Since the current [DEP] tag is for building at stage 9 only; i would like to recommend a hard dependency tag, ie [HDEP]. It can be used to build at stage 1-5, in addition to using the current dependency priority. The idea is still being able to transverse the current package database based on priority level and also being able to use hard dependency [HDEP] tags to fix the issue with "linear priority level being out-of-order ". In a scenario when a configured target fails to include a hard-dependency of a particular package; the build tool should warn the user of this issue, similar to warning dependency failure when emerging a package. Overtime, I think the hard dependency flag will create a really valuable database for resolving dependency issues; and of course, will also make t2-SDE much more friendly and powerful. The idea discussed here should not be hard to implement. In addition, at the first stage of development, we can make this option user configurable. Would you please give me your opinion? thank you,
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
