[pacman-dev] Documentation
I have merged all the changes from frugalware, and all pactests work (except for sync898 which VMiklos and I already talked about). Now, I'm on to the documentation. $ grep -ir "frugal" | grep -ve "@frugalware.com" | wc -l 385 That's without email addresses. So yeah, I didn't pay attention to the documentation patches. Most of these changes are PKGBUILD -> FrugalBuild. I think I caught all the pkg.tar.gz -> fpm and db.tar.gz -> fdb changes before patching. I'd like to see if we can some up with a decent way to allow for us to use the same documentation base, as sedding this stuff on merge seems like a waste of time. The simplest solution is to just make them all .in files and set autoconf variables like: BUILD_SCRIPT_NAME = PKGBUILD PKG_EXT = pkg.tar.gz #already discussed in the TODO etc etc Does this sound worthwhile? Are there other ideas? I'm trying to open up discussion here and look for any and all suggestions. Thanks in advance, Aaron
On Mon, Oct 09, 2006 at 09:37:35AM -0500, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
Does this sound worthwhile? Are there other ideas? I'm trying to open up discussion here and look for any and all suggestions.
hm. how can po4a handle such foo.8.in manpages? in that case should po4a be called from autogen.sh (to produce the doc/xx/foo.8.in files) then ./configure can create the doc/xx/foo.8 ones? udv / greetings, VMiklos -- Developer of Frugalware Linux, to make things frugal - http://frugalware.org
On 10/9/06, VMiklos <vmiklos@frugalware.org> wrote:
On Mon, Oct 09, 2006 at 09:37:35AM -0500, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
Does this sound worthwhile? Are there other ideas? I'm trying to open up discussion here and look for any and all suggestions.
hm. how can po4a handle such foo.8.in manpages? in that case should po4a be called from autogen.sh (to produce the doc/xx/foo.8.in files) then ./configure can create the doc/xx/foo.8 ones?
I would expect po4a to be run after configure. I mean, the only stuff that would change are proper names, which (shouldn't) be translated anyway, correct? Admittedly, I don't really know all that much about po4a, besides what I needed to install / run it. I just assumed foo.8.in -> foo.8 which is THEN picked up by po4a.
On Mon, Oct 09, 2006 at 10:04:59AM -0500, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
I would expect po4a to be run after configure. I mean, the only stuff that would change are proper names, which (shouldn't) be translated anyway, correct?
exactly
I just assumed foo.8.in -> foo.8 which is THEN picked up by po4a.
that's why po4a should be run before configure, otherwise the FrugalBuild and other strings would effect the translations i just don't know if po4a can handle the manpages if they are not in a foo.[0-9] format, since we'll have them in a foo.[0-9].in one udv / greetings, VMiklos -- Developer of Frugalware Linux, to make things frugal - http://frugalware.org
2006/10/9, Aaron Griffin <aaronmgriffin@gmail.com>:
I have merged all the changes from frugalware, and all pactests work (except for sync898 which VMiklos and I already talked about).
Now, I'm on to the documentation.
Yay! You are so fast! I suppose that was tremendous work!
Most of these changes are PKGBUILD -> FrugalBuild. I think I caught all the pkg.tar.gz -> fpm and db.tar.gz -> fdb changes before patching.
I'd like to see if we can some up with a decent way to allow for us to use the same documentation base, as sedding this stuff on merge seems like a waste of time. The simplest solution is to just make them all .in files and set autoconf variables like: BUILD_SCRIPT_NAME = PKGBUILD PKG_EXT = pkg.tar.gz #already discussed in the TODO etc etc
Does this sound worthwhile? Are there other ideas? I'm trying to open up discussion here and look for any and all suggestions.
Anyway manual review of all man pages will be needed now, after such big amount of patches. BTW, doesn't this problem with different man pages in different distros confirms my last post in "Problems with frugalware splitname changes" thread about usefulness of config schema proposed by CHristian Hamar? ;-) Config options like --with-distro=arch, --with-distro=frugalware can be used to apply changes to man pages too. -- Roman Kyrylych (Роман Кирилич)
I'd like to see if we can some up with a decent way to allow for us to use the same documentation base, as sedding this stuff on merge seems like a waste of time. The simplest solution is to just make them all .in files and set autoconf variables like: BUILD_SCRIPT_NAME = PKGBUILD PKG_EXT = pkg.tar.gz #already discussed in the TODO etc etc
Does this sound worthwhile? Are there other ideas? I'm trying to open up discussion here and look for any and all suggestions.
BTW, doesn't this problem with different man pages in different distros confirms my last post in "Problems with frugalware splitname changes" thread about usefulness of config schema proposed by CHristian Hamar? ;-) Config options like --with-distro=arch, --with-distro=frugalware can be used to apply changes to man pages too.
Hey so. That was my idea too. Using schemes not means difference imho. And not cause that it will be bad or unreadable or unmaintainable. In one of your mail Aaron, you said that you never say any program that uses #ifdef REDHAT or #ifdef DEBIAN or etc.. schema (you saw #ifdef SOLARIS, etc but that is not the same story) There are progs which uses that :) Just see gnome / network-manager or system-tools-backend. system-tools-backend works with some scheme releated thing. There are schemes for distributions. And when you compile then you specify that ./configure --with-distribution=foo Then schemas from foo will be used and all will be good, because in foo.scheme (or .in or schemes/foo.in) there is proper defines for values. At pacman we can define BUILD_SCRIPT_NAME, PKG_EXT, CACHEDIR, DB_EXT and many things which is actually hardcoded into alpm.h . And i think this will cause that pacman can be used well in new distributions, because it will be easy to customize stuffs for new distros with this scheme system. I'm not sure that we are talking the same, am i right that i see you agree with schema system that i suggested ? Regards Christian Hamar alias krix Hungary
In one of your mail Aaron, you said that you never say any program that ^^^^ errm. s/say/saw/ sorry :) typo :)
participants (4)
-
Aaron Griffin
-
Christian Hamar
-
Roman Kyrylych
-
VMiklos