Hello, this is me again reporting the progress in the Gentoo package for Pootle. The ebuild file has grown up, and I'm almost posting it in bugzilla, but I need to check some details about the dependencies.
First, let me explain how Gentoo thinks on dependencies. There are compile-time dependencies and run-time dependencies; there name is self-explanatory, There is also a mechanism called "USE flags" which configure optional dependencies and other stuff; there is no difference between "recommended" and "suggested" dependencies like Debian. 1. Does Pootle depend on the exactly same version of translate-toolkit? Ex.: 10.1 will work only with 10.1? 2. Does Pootle 10.1 depends on exactly jToolkit 0.7.8? Will any of the previous versions work? Should future jToolkit versions be compatible with Pootle 10.1? 3. Does Pootle depend directly on Kid and ElementTree, or just via jToolkit? Again question about versions. 4. Does Pootle depend on zip directly? Is any version ok? 5. Is there any other compile-time dependency of Pootle, except for Python? And now the result of my previous plans: > 1. I'll try to enhance the ebuild to create the pootle user and group. Done. > 2. I'll try to move the plain text and the three HTML documents to the > appropriate directory. Done for the plain text files; the HTML ones are useful for people already using the interface, so let's not make things complicated. > 3. If current pootle code can use .mo files were these files are > usually located, I'll try do that and tell the user that translations > of pootle itself should be done at p-w-o. Not feasible for Pootle 10.1. It would be great to do that for the next release, should I fil a bug report? > 4. I'll wait Pootle to ship with its own man pages [*] I'll just wait upstream, specially because current man pages are duplicates of information which is already available. > 5. I'll try to move the config files to /etc/pootle and create an init > script to load pootle with them. Done, but only after some work. Moving files to /etc/pootle and using command line parameters wasn't enough, Pootle couldn't find the po directory. Solved that with a symlink... Another bug report? > I was thinking about the startup user... After installing Pootle, the user receives an instruction to run a script which gets username and passwords and writes to users.prefs. I also moved the po directory to /var/lib/pootle, just like Debian. It is more FHS compliant and IMHO makes it easier for the user to find the PO files. Thanks for making and even improving Pootle! Leonardo Fontenelle ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
