how to build release-note
geert.warrink at onsnet.nu
Mon Nov 10 14:11:21 UTC 2008
> It does require common entities to be translated to get full, correct
> content. But all the appropriate locales are listed so that this should
> build properly. If the translator has not translated the common
> entities, release notes should still build correctly.
> Doing 'make html' seems to work fine here.
> Can you 'git clone' the release-notes and fedora-doc-utils (docs-common)
> repositories in a fresh location and test them there?
> Paul W. Frields
> gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
> http://paul.frields.org/ - - http://pfrields.fedorapeople.org/
> irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
In a fresh location I did:
git clone git://git.fedorahosted.org/git/docs/release-notes
git checkout -b dutch
with as result:
make: *** No rule to make target `html'. Stop.
So I assume I do something wrong.
Do you have any idea?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://lists.fedoraproject.org/pipermail/trans/attachments/20081110/ef1628e0/attachment.bin
More information about the trans