On 27 June 2011 03:20, Maciej Mrozowski <reave...@gmail.com> wrote: >> I personally prefer tabs, but I also like using EAPI="<version>", >> sorting everything alphabetically and even use the following depend blocks: > >> *DEPEND=" >> !<X-2.0 >> !Y >> <A> >> <B> >> ... >> <Z> >> a? ( <X> ) >> b? ( <Y> ) >> c? ( >> <J> >> <K> >> ) >> " > > ^^ is actually the main point of my "ebuild formatting nazi" agenda (usually > followed by "oh why did you break formatting in my shiny ebuild!11, revert!" > chants by various developers in case I happened to touch packages of theirs). > > I never understood the reason after keeping deps not sorted alphabetically > where order doesn't matter - it's like someone purposely made ebuild harder to > read - it's counter productive. >
In the case where upstream also have a rather well structured dependency list that is prone to change ( ie: perl modules ) I've found it beneficial to keep the dependencies in the same order as they use upstream. Makes it much easier to check later and makes it much easier to notice when they add a dependency -- Kent perl -e "print substr( \"edrgmaM SPA NOcomil.ic\\@tfrken\", \$_ * 3, 3 ) for ( 9,8,0,7,1,6,5,4,3,2 );" http://kent-fredric.fox.geek.nz
