On Tuesday 08 February 2005 05:53, Brian wrote:
> I think that putting special descriptions in the ebuild is best. The
> regular descriptions can be left in use.desc & use.local.desc.
> Putting the info in metadata may be easier for portage devs because it
> requires less work, but will make it a more work for everyone else
> having to edit two files.
>
> Porthole is an example of a special description for a use flag:
>
> For extra debug info I added the "debug" USE flag to cause the ebuild
> to require pycrash as a RDEPEND. The debug use flag was appropriate,
> but the normal description does not reflect what it will do for this
> ebuild.
>
> example from porthole ebuild:
>
> KEYWORDS="~x86 ~amd64 ~ppc"
> IUSE="debug"
> IDESC="debug Cause the pycrash package to be installed for porthole to
> use to get additional information about what was happening in the event
> of a program crash" DEPEND=">=dev-lang/python-2.3
>
> >=sys-apps/portage-2.0.51-r3
> >=dev-python/pygtk-2.0.0
> >=dev-python/pyxml-0.8.3"
>
> RDEPEND="${DEPEND} debug? ( >=dev-python/pycrash-0.4_pre3 )"
>
>
> [/example]
>
> I suppose multiple flag descriptions could use a comma delimiter for
> easy separation for displaying.It would probably better to do one of the following: - Have a variable per useflag. Not easy - Have different markers. Something like marking the useflag with colons e.g.: ":debug: Enable debugging support :X: Make the client aware of the X mouse" Paul -- Paul de Vrieze Gentoo Developer Mail: [EMAIL PROTECTED] Homepage: http://www.devrieze.net
pgpdItK08SULF.pgp
Description: PGP signature
