From the latest discussion on -dev i thought newdepend should only be used in eclasses, but the eclass howto says the following: "The next stage is to add any extra deps. Remember: *always* extend variables, never override! Because our goal is to avoid defining custom ebuild functions unless we have to, we set all the settings we can, and call all the helper functions we can, directly from the ebuild's main section. Remember though that there are limitations on code in the main section; for example, it must not produce any output (debug-print() output probably doesn't count though). Code listing 3.2: A simple KDE ebuild, #2: adding extra dependencies DEPEND="$DEPEND foo/bar" RDEPEND="$RDEPEND bar/foo" Alternatively, a newdepend() call will add a dep to both DEPEND and RDEPEND: Code listing 3.3: A simple KDE ebuild, #3: using newdepend() newdepend "foo? ( bar )""
i think we need to have this issue resolved first before we change the documentation in other words, we NEED nick to weigh in on what future portages are going to do (Bug 25013)
Created attachment 25840 [details, diff] Patch to eclass-howto.xml This patch removes the example ebuild that uses newdepend() and the newdepend line used in another example.
If someone can review?
yeah, but even the note on extending variables should be removed :) eclasses should be of 'normal' style, exactly like an ebuild ... portage handles the merging of the lists so if you could also change 'DEPEND="$DEPEND ...' to 'DEPEND="...' that'd be perfect
Done and committed.
