Am Donnerstag, 4. Mai 2017, 11:59:37 CEST schrieb Danny YUE:
> Hi,
> 
> As a noob in ebuild files, I got some problems while created my own
> ebuild. I googled a lot but did not really find any clue.
> 
> Let's say package A has features B and C. They are Github repositories
> and A is the entry, while B and C are submodules.
> 
> Now I want to make it three different packages respectively, and use USE
> flags to control which to install just like texlive.
> 
> 1) I know I can add USE `B' and `C' into `IUSE' variable, but if I run
> `equery u A', those flags are listed but with an "<unknown>"
> description. Where can I add some description information?

In general, these descriptions are in XML files. Globally used flags (e.g. 'X' 
or 'python') are set in the portage profiles (search for ".desc" in the 
portage tree[1]). Flags used only by certain packages are in the ebuild dir in 
metadata.xml[2]. I suggest you take a look into www-client/firefox’s 
metadata.xml, because it uses even descriptions with line breaks. (Avoid the 
look into firefox’s ebuild, though :D)

> 2) Only A has Github release URL, B and C by default should be fetched
> via `git submodule...'. How am I supposed to fetch these packages in my
> ebuild file? Download inside `src_unpack'?

Sorry, I don’t know much about git submodule. Maybe there’s something useful 
in git-r3.eclass (eclass/git-r3.eclass).
 
> Any help is appreciated. Thanks in advance.
> 
> 
> Danny

[1] find /usr/portage/ -iname "*desc"
[2] find /usr/portage/ -iname "*metadata.xml"

Nils

PS: Great you write ebuilds - keep going on and suggest bugfixes for broken 
ebuilds later! :)

-- 
GPG fingerprint: '00EF D31F 1B60 D5DB ADB8  31C1 C0EC E696 0E54 475B'
Nils Freydank

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to