You just need to update Yelp and gnome-doc-utils to the current 2.28 versions - I did this on my Foresight system back in June when the first tarball releases came out just by updating the version numbers in the recipe and cooking and installing locally. There are no other dependencies, so if you're writing the doc, there's no reason you can't upgrade now. By the time the user guide is updated, GNOME 2.28 would be out.
Paul On Thu, Sep 3, 2009 at 1:40 PM, Alexandre Franke <alexandre.fra...@gmail.com > wrote: > On Thu, Sep 3, 2009 at 8:28 PM, Og Maciel<ogmac...@gnome.org> wrote: > > I'd like to ask the opinion of you guys about moving the > > foresight-user-guide-2 source code from our Hg setup to Gitorious. My > > objective is to allow for easier consumption by collaborators and avoid > > the need of adding new ssh keys for every person we want to grant commit > > access. Also, people can easily fork and request merges from Gitorious. > > +1 on that from me. > > > I also want to propose that we move away from Docbooks and move to > > Mallard. I started scouting around and I'd like to make Foresight User > > Guide something that the Mallard guys can refer to as a success story > > (while we at the same time get some much needed face lift). > > I am indeed in favor of the change and would be really pleased to do a > big part of this work. > > BUT > > As far as I know, yelp doesn't officially support Mallard yet. > Remember that we're still shipping GNOME/yelp 2.26.x and that Mallard > will only be supported from 2.28.x. > > I know, 2.28 is not that far but it's not there yet. > > -- > Alexandre Franke > _______________________________________________ > Foresight-devel mailing list > Foresight-devel@lists.rpath.org > http://lists.rpath.org/mailman/listinfo/foresight-devel > _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
