[PHP-DOC] Re: [SVN-MIGRATION] SVN PHPDOC
On Tue, Jul 14, 2009 at 01:47, Gwynne Raskindgwy...@darkrainfall.org wrote: On Jul 13, 2009, at 9:08 AM, Hannes Magnusson wrote: When I checkedout phpdoc using TortoiseCVS, I got (as far as I can tell) what svn has as ... http://svn.php.net/repository/phpdoc/doc-base/trunk/ and http://svn.php.net/repository/phpdoc/en/trunk/ [...] So, windows is currently unable to build docs. Or have I missed something? We'll need to create helper modules, like the magical phpdoc-lang modules we used to have in CVS (which pulled both en and lang), which have sets of svn:externals. f.e. /repository/phpdoc/doc-en svn:externals . /repository/phpdoc/doc-base/trunk svn:externals ./en /repository/phpdoc/en/trunk /repository/phpdoc/doc-ja svn:externals . /repository/phpdoc/doc-base/trunk svn:externals ./ja /repository/phpdoc/ja/trunk /repository/phpdoc/doc-all svn:externals . /repository/phpdoc/doc-base/trunk svn:externals ./en /repository/phpdoc/en/trunk svn:externals ./ja /repository/phpdoc/ja/trunk No, in fact we don't actually need that, and it's not a Windows issue. It's an issue with no one having updated configure.php for the new setup. If someone could, you know, get around to doing that like I've been screaming for a year, *Lumbergh* that'd be great. If you deeply insist on the pointless stupid useless magical things, you can add them. How exactly is it stupid to checkout one helper module vs checking out 15 translations, english and doc-base, and making sure everything is in the correct places? Everysingle person needs to do this (granted, most only 3modules), and by definition thats what svn:externals where aimed to fix. I see no reason why we can't simplify checkouts, and I can't see how that can possible be stupid. -Hannes
[PHP-DOC] Problem committing to phpdoc
Output from TortoiseSVN is ... Command: Commit Modified: D:\Personal Files\Downloads\Software\Programming\PHP\Checkouts\svn.php.net\phpdoc\doc-base\manual.xml.in Sending content: D:\Personal Files\Downloads\Software\Programming\PHP\Checkouts\svn.php.net\phpdoc\doc-base\manual.xml.in Error: Commit failed (details follow): Error: Commit blocked by pre-commit hook (exit code 1) with output: Error: *** Error: Access denied: Insufficient karma for rquadling to svnlook: Unknown memcached Error: error while reading: The timeout specified has expired. Error: Contact gr...@php.net for access. Finished!: Previously had access on CVS ... Revision: 273089 Author: rquadling Date: 17:09:18, 08 January 2009 Message: Better test for Non windows. Modified : /phpdoc/doc-base/trunk/scripts/file-entities.php.in -- - Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498r=213474731 Standing on the shoulders of some very clever giants! ZOPA : http://uk.zopa.com/member/RQuadling
[PHP-DOC] Re: [SVN-MIGRATION] SVN PHPDOC
2009/7/14 Philip Olson phi...@roshambo.org:
Or have I missed something?
This is now fixed as of a couple of minutes ago but I cannot test on Windows
so please do that. The only problem I see now is with images/figures, likely
to do with PhD (the build system).
Regards,
Philip
Found and hopefully fixed the build issues. Well, at least on windows...
I've lost commit karma, so patch is below and attached.
Regards,
Richard Quadling.
Index: manual.xml.in
===
--- manual.xml.in (revision 284062)
+++ manual.xml.in (working copy)
@@ -14,9 +14,9 @@
%isopub;
!-- Add translated specific definitions and snippets --
-!ENTITY % language-defs SYSTEM ./@LANGDIR@/language-defs.ent
-!ENTITY % language-snippets SYSTEM ./@LANGDIR@/language-snippets.ent
-!ENTITY % extensionsSYSTEM ./@LANGDIR@/extensions.ent
+!ENTITY % language-defs SYSTEM ../@LANGDIR@/language-defs.ent
+!ENTITY % language-snippets SYSTEM ../@LANGDIR@/language-snippets.ent
+!ENTITY % extensionsSYSTEM ../@LANGDIR@/extensions.ent
%language-defs;
%extensions;
Property changes on: scripts
___
Modified: svn:ignore
- entities.*.xml
+ entities.*.xml
file-entities.php
Index: scripts/file-entities.php.in
===
--- scripts/file-entities.php.in(revision 284061)
+++ scripts/file-entities.php.in(working copy)
@@ -303,7 +303,7 @@
if ($filename == ) {
return sprintf(!ENTITY %-40s''\n, $entname);
} else {
-return sprintf(!ENTITY %-40s SYSTEM '%s'\n, $entname,
str_replace(str_replace(\\, /, $GLOBALS['out_dir']), '..',
str_replace(\\, /, $filename)));
+return sprintf(!ENTITY %-40s SYSTEM 'file:///%s'\n,
$entname, str_replace(str_replace(\\, /, $GLOBALS['out_dir']),
'..', str_replace(array(\\, ), array(/, %20), $filename)));
}
}
--
-
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498r=213474731
Standing on the shoulders of some very clever giants!
ZOPA : http://uk.zopa.com/member/RQuadling
Index: manual.xml.in
===
--- manual.xml.in (revision 284062)
+++ manual.xml.in (working copy)
@@ -14,9 +14,9 @@
%isopub;
!-- Add translated specific definitions and snippets --
-!ENTITY % language-defs SYSTEM ./@LANGDIR@/language-defs.ent
-!ENTITY % language-snippets SYSTEM ./@LANGDIR@/language-snippets.ent
-!ENTITY % extensionsSYSTEM ./@LANGDIR@/extensions.ent
+!ENTITY % language-defs SYSTEM ../@LANGDIR@/language-defs.ent
+!ENTITY % language-snippets SYSTEM ../@LANGDIR@/language-snippets.ent
+!ENTITY % extensionsSYSTEM ../@LANGDIR@/extensions.ent
%language-defs;
%extensions;
Property changes on: scripts
___
Modified: svn:ignore
- entities.*.xml
+ entities.*.xml
file-entities.php
Index: scripts/file-entities.php.in
===
--- scripts/file-entities.php.in(revision 284061)
+++ scripts/file-entities.php.in(working copy)
@@ -303,7 +303,7 @@
if ($filename == ) {
return sprintf(!ENTITY %-40s''\n, $entname);
} else {
-return sprintf(!ENTITY %-40s SYSTEM '%s'\n, $entname,
str_replace(str_replace(\\, /, $GLOBALS['out_dir']), '..',
str_replace(\\, /, $filename)));
+return sprintf(!ENTITY %-40s SYSTEM 'file:///%s'\n, $entname,
str_replace(str_replace(\\, /, $GLOBALS['out_dir']), '..',
str_replace(array(\\, ), array(/, %20), $filename)));
}
}
[PHP-DOC] Re: [SVN-MIGRATION] SVN PHPDOC
On Jul 14, 2009, at 5:40 AM, Richard Quadling wrote: Or have I missed something? This is now fixed as of a couple of minutes ago but I cannot test on Windows so please do that. The only problem I see now is with images/ figures, likely to do with PhD (the build system). Found and hopefully fixed the build issues. Well, at least on windows... I've lost commit karma, so patch is below and attached. You haven't lost commit karma. There was an error with memcached that was messing with everything. The server should be back to normal now. -- Gwynne
[PHP-DOC] .manual.xml output
Hi. Now that the languages are external to phpdoc, should the .manual.xml file produced by phpdoc's configure.php be saved in @lang...@? Richard -- - Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498r=213474731 Standing on the shoulders of some very clever giants! ZOPA : http://uk.zopa.com/member/RQuadling
[PHP-DOC] Translating php manual into Persian
hi there, I'd like to help translate php manual into persian. there's a page for Persian manual but unfortunately no part is translated. I want to know how to start it. Maybe i need a quick start guide or HOWTO. Thanks in advance, Daniel
[PHP-DOC] Intro and quick patches
Hi all, I'm a long time PHP user, lost track of how long exactly but since late v4 days. I've followed various PHP lists to keep up to date on developments, but not being a CVS user I've not been able to contribute much back. The switch to SVN has been greatly anticipated. I tried getting phd installed tonight, but had problems connecting to the channel with PEAR. So instead of looking around the main docs I started looking at phd from SVN instead. Here are two patches which change references from CVS to SVN in a couple of the phd readme/howto files. -- Niel Archer niel.archer (at) blueyonder.co.uk phd_HOWTO.GENERATE_CHM.diff Description: Binary data phd_README.diff Description: Binary data
Re: [PHP-DOC] Intro and quick patches
On Tue, Jul 14, 2009 at 22:26, Niel Archern...@chance.now wrote: I tried getting phd installed tonight, but had problems connecting to the channel with PEAR. So instead of looking around the main docs I started looking at phd from SVN instead. Hah! Thats how contribution should start - fixing the things that you need to use to contribute :D I was gonna tell you that you could download the release tgz from http://doc.php.net/phd but apparently doc.php.net is having more problems then just the pear channel.. I'll have to look into it tomorrow morning if Philip hasn't by then (although I think he is in the middle of updating everything to use SVN on the server as we speak^Wwrite). Regarding the patches; you are adding Windows line endings.. make sure your editor is configured correctly :) Note: Our summer of code student, Moacir, is doing quite drastic changes in HEAD (trunk).. it may or may not work :) Using PhD from the PHD_0_4 branch however should work fine, as that is the current release branch. -Hannes
[PHP-DOC] Re: [PHP-CVS] Commit freeze is officially over
On Jul 14, 2009, at 4:36 PM, Knut Urdalen wrote: Any other issues, please bring them to my attention. Preferably via email, not IRC :). Are we going to have a similar page like the one for Anonymous CVS Access [1] for svn.php.net? Please in the future avoid cross-posting to seven lists; use svn- migration@ for this kind of question. To answer the question, anonsvn.php has already been commited to phpweb and should show up as soon as we get rsync back in service. -- Gwynne
[PHP-DOC] Re: [PHP-CVS] Commit freeze is officially over
Gwynne Raskind wrote: Any other issues, please bring them to my attention. Preferably via email, not IRC :). Are we going to have a similar page like the one for Anonymous CVS Access [1] for svn.php.net? Knut [1] http://www.php.net/anoncvs.php
Re: [PHP-DOC] Intro and quick patches
On Tue, Jul 14, 2009 at 22:26, Niel Archern...@chance.now wrote: I tried getting phd installed tonight, but had problems connecting to the channel with PEAR. So instead of looking around the main docs I started looking at phd from SVN instead. Hah! Thats how contribution should start - fixing the things that you need to use to contribute :D I was gonna tell you that you could download the release tgz from http://doc.php.net/phd but apparently doc.php.net is having more problems then just the pear channel.. I'll have to look into it tomorrow morning if Philip hasn't by then (although I think he is in the middle of updating everything to use SVN on the server as we speak^Wwrite). Regarding the patches; you are adding Windows line endings.. make sure your editor is configured correctly :) Very sorry. Hadn't realised there was a conversion going on. Unfortunately, it's not my editor doing it. It's SVN. The properties on the files themselves contain svn:eol-style native, forcing them to CRLF on a Windows machine. Annoying, as I'm using Eclipse and have it set up to default to UTF-8 encoding and Unix line endings ;-) Should I resend them converted? Note: Our summer of code student, Moacir, is doing quite drastic changes in HEAD (trunk).. it may or may not work :) Using PhD from the PHD_0_4 branch however should work fine, as that is the current release branch. Ahh, OK. Thanks. I grabbed the trunk and tried installing that with PEAR also. PEAR didn't like the package.xml contents, so I will try the the the branch version. -Hannes -- Niel Archer niel.archer (at) blueyonder.co.uk
Re: [PHP-DOC] Intro and quick patches
On Jul 14, 2009, at 4:10 PM, Niel Archer wrote: On Tue, Jul 14, 2009 at 22:26, Niel Archern...@chance.now wrote: I tried getting phd installed tonight, but had problems connecting to the channel with PEAR. So instead of looking around the main docs I started looking at phd from SVN instead. Hah! Thats how contribution should start - fixing the things that you need to use to contribute :D I was gonna tell you that you could download the release tgz from http://doc.php.net/phd but apparently doc.php.net is having more problems then just the pear channel.. I'll have to look into it tomorrow morning if Philip hasn't by then (although I think he is in the middle of updating everything to use SVN on the server as we speak^Wwrite). Regarding the patches; you are adding Windows line endings.. make sure your editor is configured correctly :) Very sorry. Hadn't realised there was a conversion going on. Unfortunately, it's not my editor doing it. It's SVN. The properties on the files themselves contain svn:eol-style native, forcing them to CRLF on a Windows machine. Annoying, as I'm using Eclipse and have it set up to default to UTF-8 encoding and Unix line endings ;-) Everything should be fine now. Actually that's not true, but most things seem fine or close to working. Still some tweaking needs done with docweb+svn, a euk2 cron or three may be yelling at us, but the aforementioned site and phd pear channel work now. Should I resend them converted? Yeah, also note a couple typos in there that turned 'phpdoc' checkouts into 'phd'. Note: Our summer of code student, Moacir, is doing quite drastic changes in HEAD (trunk).. it may or may not work :) Using PhD from the PHD_0_4 branch however should work fine, as that is the current release branch. Ahh, OK. Thanks. I grabbed the trunk and tried installing that with PEAR also. PEAR didn't like the package.xml contents, so I will try the the the branch version. The channel should work fine now. 'pear install phpdocs/phd-beta' Regards, Philip
Re: [PHP-DOC] Intro and quick patches
Should I resend them converted? Yeah, also note a couple typos in there that turned 'phpdoc' checkouts into 'phd'. Diffs attached. -- Niel Archer niel.archer (at) blueyonder.co.uk phd_README.diff Description: Binary data phd_HOWTO.GENERATE_CHM.diff Description: Binary data
Re: [PHP-DOC] Intro and quick patches
Hi Everything should be fine now. Actually that's not true, but most things seem fine or close to working. Still some tweaking needs done with docweb+svn, a euk2 cron or three may be yelling at us, but the aforementioned site and phd pear channel work now. doc.php.net channel is working again. ;-) However the phd installed doesn't appear to be a working version. i.e. there is no phd.bat file created which makes it is unusable on WIndows I'd guess. I also tried using the PHD_0_4 branch from SVN. and doing: pear install -f package.xml It gave me the same installation. Using PHP v5.3.0, PEAR 1.8.1 Regards, Philip -- Niel Archer niel.archer (at) blueyonder.co.uk
Re: [PHP-DOC] Intro and quick patches
On Jul 14, 2009, at 4:36 PM, Niel Archer wrote: Should I resend them converted? Yeah, also note a couple typos in there that turned 'phpdoc' checkouts into 'phd'. Diffs attached. This diff brings up a good point for us to discuss. What is the preferred method to check something out from SVN? Most anything we do requires at least two SVN checkouts. A classic example for English: - cd /where/doc/stuff/is/stored - svn co http://svn.php.net/repository/phpdoc/en/trunk phpdoc/en - svn co http://svn.php.net/repository/phpdoc/doc-base/trunk phpdoc/ doc-base Leaving us with en and doc-base directories. And then for phpdoc-all it gets trickier, well, a lot longer. The choices seem to be either: - use svn:externals - create and promote scripts for this - change our structure/layout - ... ? I don't understand the pros and cons of using svn:externals but the topic seems to have a holy war type feel to it. Is this true and/or avoidable? What are the pros and cons? If a script is used, I imagine it'd be stored in doc-base then used to checkout languages. I also imagine other places at php.net would use it (or svn:externals). Regards, Philip
Re: [PHP-DOC] Intro and quick patches
This diff brings up a good point for us to discuss. What is the preferred method to check something out from SVN? Most anything we do requires at least two SVN checkouts. A classic example for English: - cd /where/doc/stuff/is/stored - svn co http://svn.php.net/repository/phpdoc/en/trunk phpdoc/en - svn co http://svn.php.net/repository/phpdoc/doc-base/trunkphpdoc/doc-base Leaving us with en and doc-base directories. And then for phpdoc-all it gets trickier, well, a lot longer. The choices seem to be either: - use svn:externals - create and promote scripts for this - change our structure/layout - ... ? I don't understand the pros and cons of using svn:externals but the topic seems to have a holy war type feel to it. Is this true and/or avoidable? What are the pros and cons? If a script is used, I imagine it'd be stored in doc-base then used to checkout languages. I also imagine other places at php.net would use it (or svn:externals). using svn:externals have some restrictions ( http://svnbook.red-bean.com/en/1.0/ch07s03.html) First, an externals definition can only point to directories, not files. Second, the externals definition cannot point to relative paths (paths like ../../skins/myskin). Third, the working copies created via the externals definition support are still disconnected from the primary working copy (on whose versioned directories thesvn:externals property was actually set). And Subversion still only truly operates on non-disjoint working copies. So, for example, if you want to commit changes that you've made in one or more of those external working copies, you must run svn commit explicitly on those working copies—committing on the primary working copy will not recurse into any external ones. And, svn:externals does not have a prompt so everything will be checkout-ed for everyone by the externals definition. ks
Re: [PHP-DOC] Intro and quick patches
KSChan wrote: And, svn:externals does not have a prompt so everything will be checkout-ed for everyone by the externals definition. This is not necessarily true, see http://svn.pear.php.net/wsvn/PEARSVN?op=compcompare[]=%2f...@663compare[]=%2f...@837 for an example of how to make a straight checkout do a whole bunch of externals checkouts. one simply does svn co http://svn.pear.php.net/PEAR2/all Greg
Re: [PHP-DOC] Translating php manual into Persian
Hi dear daniel The translations are in http://svn.php.net/viewvc/phpdoc/fa/trunk/ and they are going on. There will be some changes in translation files of phpdoc so I have put a hold on committing new translations for now until changes are complete. So if you would like to, please send me some of your translations. Regards. Pedram On Tue, Jul 14, 2009 at 9:15 PM, Daniel Rahmanzadeh dan...@gmail.comwrote: hi there, I'd like to help translate php manual into persian. there's a page for Persian manual but unfortunately no part is translated. I want to know how to start it. Maybe i need a quick start guide or HOWTO. Thanks in advance, Daniel
