Re: svn-export Re: svn bdb checkout?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/24/13 5:16 PM, Xyne wrote: Greg Larkin wrote: Hi Xyne, Thanks for turning that around so quickly, and I am doing some testing here with the idea to incorporate svn-export into the FreeBSD ports tree. I've run into a couple of problems that I hope you can take a look at it: - - Changesets containing directory or file deletions cause the script to exit. Here is an example where I fetched the FreeBSD ports tree at a particular revision, then attempted to update to the latest revision: # python3 svn-export --revision-file foo2.dat http://svn.freebsd.org/head/ports-mgmt ports-mgmt Determining current revision. Current revision is 310894. Determining changes [31:310894]. 16 new/modified files, 5 deletions Traceback (most recent call last): File svn-export, line 407, in module svn.main() File svn-export, line 380, in main self.remove_old_files(deleted) File svn-export, line 302, in remove_old_files os.unlink(path) PermissionError: [Errno 1] Operation not permitted: 'ports-mgmt/pkg/files' - - I can't get the --to-script option to work if there are any file/directory deletions in the changeset. It looks like the actual deletion operations are attempted (like above) even when the - --to-script option is selected. Let me know if you need any other information. Thank you, Greg Hi, I think I have fixed both errors in svn-export-2013.1.24, along with another directory-related error that I discovered while debugging (attempts to cat new directories in incremental exports instead of recursing them). Please try again and let me know if it works. If not, please post steps to reproduce the error with a publicly accessible repo. I was unable to access the ports-mgmt repos in your example. Hi Xyne, I mistyped the repository URL in my previous email, and I just captured a session that displays an error similar to the one above. Note that I pre-seeded the environment with a rev.dat file containing the string 31. I did that to simulate an incremental fetch, as you'll see here: # python3 svn-export -r 31 http://svn.freebsd.org/ports/head/ports-mgmt ports-mgmt Exporting new repository. Exported revision 31 # python3 svn-export --revision-file rev.dat http://svn.freebsd.org/ports/head/ports-mgmt ports-mgmt Determining current revision. Current revision is 310981. Determining changes [31:310981]. 16 new/modified files, 5 deletions Traceback (most recent call last): File svn-export, line 459, in module svn.main() File svn-export, line 432, in main self.remove_old_files(deleted) File svn-export, line 310, in remove_old_files os.unlink(path) PermissionError: [Errno 1] Operation not permitted: 'ports-mgmt/pkg/files' # exit As far as I can tell, svn-export attempts to remove a directory before the file contained within that directory. It seems like PermissionError isn't the best error code for Python to throw in that case, since it appears to mask the root problem. Can you re-order the deletes so all files are deleted first, then directories are deleted in a bottom-up sequence? I think that will solve this problem. Incidentally, if anyone is looking at the code for svn-export, feel free to suggest a better way to incrementally export new subdirectories (see the get_new_files() method). I'll take a look at that soon to see if there are any possible optimizations. Incidentally, my release scripts do not leave old source archives on the server for very long after a new release and I tend to update often when I can. If you need me to increase the shelf life of old archives to prevent 404's, let me know (give me a reasonable interval and I will update my scripts). In the future I may switch to posting my private Git repos, but I tend to rewrite history and I know that really irks people. Regards, Xyne Once we create a port for svn-export, we typically point to the original download site in the port Makefile. It's a good idea for the port maintainer to find a mirror site and include that too, but if not, all distro files are eventually mirrored to the FreeBSD cluster. Ideally, the source distros remain in place forever or at least until the FreeBSD port is updated to the latest version, but if that's not possible, I can mirror the files too. Thank you, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlECp3EACgkQ0sRouByUApDo2gCfRLq1/7Cl40y7GDShUOamQTMr aqQAn0IPLS/nkcyjOadEA3cKzuoDc0Wp =3JN4 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe,
Re: svn-export Re: svn bdb checkout?
Greg Larkin wrote: # python3 svn-export -r 31 http://svn.freebsd.org/ports/head/ports-mgmt ports-mgmt Exporting new repository. Exported revision 31 # python3 svn-export --revision-file rev.dat http://svn.freebsd.org/ports/head/ports-mgmt ports-mgmt Determining current revision. Current revision is 310981. Determining changes [31:310981]. 16 new/modified files, 5 deletions Traceback (most recent call last): File svn-export, line 459, in module svn.main() File svn-export, line 432, in main self.remove_old_files(deleted) File svn-export, line 310, in remove_old_files os.unlink(path) PermissionError: [Errno 1] Operation not permitted: 'ports-mgmt/pkg/files' # exit As far as I can tell, svn-export attempts to remove a directory before the file contained within that directory. It seems like PermissionError isn't the best error code for Python to throw in that case, since it appears to mask the root problem. On Arch Linux, Python raises the expected IsADirectoryError exception. Perhaps PermissionError is due to a bug in Python 3 on FreeBSD. It would not be the first exception bug that I have encountered (e.g. os.makedirs(..., exist_ok=True) raises FileExists when permissions differ on existing directories... very confusing the first time it shows up). Regardless, svn-export now tries to remove a directory in both cases. Please updated to version 2013.1.25 and let me know if it works on FreeBSD. Incidentally, if anyone is looking at the code for svn-export, feel free to suggest a better way to incrementally export new subdirectories (see the get_new_files() method). I'll take a look at that soon to see if there are any possible optimizations. Ok, thanks. Once we create a port for svn-export, we typically point to the original download site in the port Makefile. It's a good idea for the port maintainer to find a mirror site and include that too, but if not, all distro files are eventually mirrored to the FreeBSD cluster. Ideally, the source distros remain in place forever or at least until the FreeBSD port is updated to the latest version, but if that's not possible, I can mirror the files too. I have changed the time-to-live to 6 months for old archives. Regards, Xyne ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: svn-export Re: svn bdb checkout?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/25/13 1:53 PM, Xyne wrote: Greg Larkin wrote: # python3 svn-export -r 31 http://svn.freebsd.org/ports/head/ports-mgmt ports-mgmt Exporting new repository. Exported revision 31 # python3 svn-export --revision-file rev.dat http://svn.freebsd.org/ports/head/ports-mgmt ports-mgmt Determining current revision. Current revision is 310981. Determining changes [31:310981]. 16 new/modified files, 5 deletions Traceback (most recent call last): File svn-export, line 459, in module svn.main() File svn-export, line 432, in main self.remove_old_files(deleted) File svn-export, line 310, in remove_old_files os.unlink(path) PermissionError: [Errno 1] Operation not permitted: 'ports-mgmt/pkg/files' # exit As far as I can tell, svn-export attempts to remove a directory before the file contained within that directory. It seems like PermissionError isn't the best error code for Python to throw in that case, since it appears to mask the root problem. On Arch Linux, Python raises the expected IsADirectoryError exception. Perhaps PermissionError is due to a bug in Python 3 on FreeBSD. It would not be the first exception bug that I have encountered (e.g. os.makedirs(..., exist_ok=True) raises FileExists when permissions differ on existing directories... very confusing the first time it shows up). Regardless, svn-export now tries to remove a directory in both cases. Please updated to version 2013.1.25 and let me know if it works on FreeBSD. Yes, it does work on FreeBSD now, but I suggest investigating whether it's possible to reorder the removal list with files first, then directories. That way, you won't have to rely on an exception to determine if a directory to be removed is not empty yet. The os.walk() method looks like it would be useful here: http://docs.python.org/3/library/os.html?highlight=os.walk#os.walk Incidentally, if anyone is looking at the code for svn-export, feel free to suggest a better way to incrementally export new subdirectories (see the get_new_files() method). I'll take a look at that soon to see if there are any possible optimizations. Ok, thanks. I looked at the method, and my first idea was to svn cat as many files at once as possible, up to the maximum command line length. You will avoid spawning a lot of svn processes and opening new network connections each time. If the threads option is 1, you could divide the maximum command line length by that number and keep filling in filenames up to that limit in each child process. I expect you would also get a nice performance boost if you changed from spawning svn commands to the Python SVN bindings. Here's an example of how it works: http://svn.apache.org/repos/asf/subversion/trunk/tools/examples/getfile.py Once we create a port for svn-export, we typically point to the original download site in the port Makefile. It's a good idea for the port maintainer to find a mirror site and include that too, but if not, all distro files are eventually mirrored to the FreeBSD cluster. Ideally, the source distros remain in place forever or at least until the FreeBSD port is updated to the latest version, but if that's not possible, I can mirror the files too. I have changed the time-to-live to 6 months for old archives. Excellent, thank you. Hope that all helps, Greg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlEC/ooACgkQ0sRouByUApCa0wCfQr4rIT9oQrI3LkYPlMGbfCnj KqoAniabxFC2xeNAzvdLHLYhXhxYs1xi =cfUS -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: svn-export Re: svn bdb checkout?
Greg Larkin wrote: Hi Xyne, Thanks for turning that around so quickly, and I am doing some testing here with the idea to incorporate svn-export into the FreeBSD ports tree. I've run into a couple of problems that I hope you can take a look at it: - - Changesets containing directory or file deletions cause the script to exit. Here is an example where I fetched the FreeBSD ports tree at a particular revision, then attempted to update to the latest revision: # python3 svn-export --revision-file foo2.dat http://svn.freebsd.org/head/ports-mgmt ports-mgmt Determining current revision. Current revision is 310894. Determining changes [31:310894]. 16 new/modified files, 5 deletions Traceback (most recent call last): File svn-export, line 407, in module svn.main() File svn-export, line 380, in main self.remove_old_files(deleted) File svn-export, line 302, in remove_old_files os.unlink(path) PermissionError: [Errno 1] Operation not permitted: 'ports-mgmt/pkg/files' - - I can't get the --to-script option to work if there are any file/directory deletions in the changeset. It looks like the actual deletion operations are attempted (like above) even when the - --to-script option is selected. Let me know if you need any other information. Thank you, Greg Hi, I think I have fixed both errors in svn-export-2013.1.24, along with another directory-related error that I discovered while debugging (attempts to cat new directories in incremental exports instead of recursing them). Please try again and let me know if it works. If not, please post steps to reproduce the error with a publicly accessible repo. I was unable to access the ports-mgmt repos in your example. Incidentally, if anyone is looking at the code for svn-export, feel free to suggest a better way to incrementally export new subdirectories (see the get_new_files() method). Incidentally, my release scripts do not leave old source archives on the server for very long after a new release and I tend to update often when I can. If you need me to increase the shelf life of old archives to prevent 404's, let me know (give me a reasonable interval and I will update my scripts). In the future I may switch to posting my private Git repos, but I tend to rewrite history and I know that really irks people. Regards, Xyne ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: svn-export Re: svn bdb checkout?
Hello. 2013/01/18 23:50:17 + Xyne x...@archlinux.ca = To Warren Block : X On 2013-01-17 21:32 -0700 X Warren Block wrote: X X A working version in any language would be great. A better version in X Python would be nice, too, but it's the working part that's important. X X There's a difference between working and working on a random system with X unexpectedly disabled features. The current version works in the former sense. I suppose the latter is what the perl5 in general and cpan (cpan-testers at the least) was always considered to be about. I'd disclose that following TIMTOWTDI the so called 'modern perl' and a 'perl6' can be used to reconsider on this. For the case of following the former line the switch to python may (or may not) happen to be the (good) difference about such a freebsd-related task. Will see. Thank you. -- Peter Vereshagin pe...@vereshagin.org (http://vereshagin.org) pgp: 1754B9C1 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: svn-export Re: svn bdb checkout?
On Sat, 19 Jan 2013, Xyne wrote: svn-export has now been rewritten in Python 3. Here's a quick list of changes/features: * threads have been replaced with forks (and remain optional) * new option to set svn binary * new option to generate shell script instead of using internal calls * no subshell invocation * only svn binary is called directly I've only done some quick testing. Let me know how it works. Very cool! It will be a bit before I can try it, but hopefully others will also. Oh, and the URL: http://xyne.archlinux.ca/projects/svn-export/ Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: svn-export Re: svn bdb checkout?
Hello. 2013/01/17 21:32:08 -0700 Warren Block wbl...@wonkity.com = To Xyne : WB On Fri, 18 Jan 2013, Xyne wrote: WB WB I'm the author of svn-export. I haven't really touched the code since I wrote WB it in 2009 and back then I tended to write most things in noobish Perl. I shouldn't name your 2009 Perl that bad. ;-) WB Although it should not be difficult to replace threading with forking (and I WB agree that Perl threading is generally to be avoided), I think I would rather WB just rewrite it cleanly in Python. Among other things it will simplify argument WB parsing and subprocess invocation via standard library functions. No objection. As a bonus it will run on fork()less ms-windows. WB This would be in Python 3 but I could try to restrict it to be compatible with WB Python 2 if necessary. I have no idea if it is. I use python only as a build dependency yet and for my pretty old freebsd the versions are: python26-2.6.7_3 python27-2.7.3 WB Would that be better than patching/porting the current Perl version? If so then WB I will put it on my todo list, but I am unlikely to have any time in the coming WB weeks to work on it. I don't know which one is best. Some proposals I will draft later believing those are language-independent. I know svn has some perl bindings I think just for the scripts like 'svn-export' I wish it used. Does svn have ones for python also? WB A working version in any language would be great. A better version in WB Python would be nice, too, but it's the working part that's important. WB WB Incidentally, when looking at the code now I noticed that there were some SVN WB options missing. I have added those in today's release. Wow. ;-) WB p.s. I have not subscribed to this list, so please keep me in CC if you would WB like me to reply (in case this isn't done automatically). WB WB It's standard procedure for the FreeBSD lists. Good I know this, too. Thank you. -- Peter Vereshagin pe...@vereshagin.org (http://vereshagin.org) pgp: 1754B9C1 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: svn-export Re: svn bdb checkout?
On 2013-01-17 21:32 -0700 Warren Block wrote: A working version in any language would be great. A better version in Python would be nice, too, but it's the working part that's important. There's a difference between working and working on a random system with unexpectedly disabled features. The current version works in the former sense. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: svn-export Re: svn bdb checkout?
Hi, svn-export has now been rewritten in Python 3. Here's a quick list of changes/features: * threads have been replaced with forks (and remain optional) * new option to set svn binary * new option to generate shell script instead of using internal calls * no subshell invocation * only svn binary is called directly I've only done some quick testing. Let me know how it works. Regards, Xyne ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: svn-export Re: svn bdb checkout?
Peter Vereshagin wrote: I believe 'amd64' is the common architecture these days and 'perl malloc' is the feature needed for profiling and/or leaks detection. Good news is that such a stuff can be redone with forks instead of threads but it should take me the time amount I'm not supposed to have of the any early. By itself perl threading has a fabulously bad luck history, recently criticized for instance at: https://speakerdeck.com/stevan_little/perl-is-not-dead-it-is-a-dead-end Thank you. Hi, I'm the author of svn-export. I haven't really touched the code since I wrote it in 2009 and back then I tended to write most things in noobish Perl. Although it should not be difficult to replace threading with forking (and I agree that Perl threading is generally to be avoided), I think I would rather just rewrite it cleanly in Python. Among other things it will simplify argument parsing and subprocess invocation via standard library functions. This would be in Python 3 but I could try to restrict it to be compatible with Python 2 if necessary. Would that be better than patching/porting the current Perl version? If so then I will put it on my todo list, but I am unlikely to have any time in the coming weeks to work on it. Incidentally, when looking at the code now I noticed that there were some SVN options missing. I have added those in today's release. Regards, Xyne p.s. I have not subscribed to this list, so please keep me in CC if you would like me to reply (in case this isn't done automatically). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: svn-export Re: svn bdb checkout?
On Fri, 18 Jan 2013, Xyne wrote: I'm the author of svn-export. I haven't really touched the code since I wrote it in 2009 and back then I tended to write most things in noobish Perl. Although it should not be difficult to replace threading with forking (and I agree that Perl threading is generally to be avoided), I think I would rather just rewrite it cleanly in Python. Among other things it will simplify argument parsing and subprocess invocation via standard library functions. This would be in Python 3 but I could try to restrict it to be compatible with Python 2 if necessary. Would that be better than patching/porting the current Perl version? If so then I will put it on my todo list, but I am unlikely to have any time in the coming weeks to work on it. A working version in any language would be great. A better version in Python would be nice, too, but it's the working part that's important. Incidentally, when looking at the code now I noticed that there were some SVN options missing. I have added those in today's release. Regards, Xyne p.s. I have not subscribed to this list, so please keep me in CC if you would like me to reply (in case this isn't done automatically). It's standard procedure for the FreeBSD lists. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
svn-export Re: svn bdb checkout?
Hello. 2013/01/16 15:24:00 -0500 Greg Larkin glar...@freebsd.org = To Peter Vereshagin : GL On 1/16/13 3:07 PM, Peter Vereshagin wrote: GL 2013/01/16 13:51:42 -0600 Joseph A. Nagy, Jr GL jnagyjr1...@gmail.com = To Peter Vereshagin : JANJ On 01/16/13 GL 13:35, Peter Vereshagin wrote: JANJ 2013/01/16 13:19:19 -0600 GL The fsfs and bdb backends refer only to the server side of the GL Subversion repository. Each one represents a different way of storing Ouch! there's the difference that Git made me to forget about, sorry. GL the repository data on the server side and doesn't have any bearing on GL the .svn directory inside of a client-side working copy. GL GL Also note that in earlier versions of the Subversion client, .svn GL directories were created at all levels of the working copy. Since GL 1.7, there is one .svn directory per working copy, but that doesn't GL have anything to do with the backend repository format. Cool. Heard it but was googled into the wrong direction. GL In short, svn export is the way to pull source code out of a GL Subversion repository with the .svn directory. However, that command Will try. Stuck with: $ xz -d svn-export-2012.12.24.1.tar.xz xz: svn-export-2012.12.24.1.tar.xz: File format not recognized Shall I update from 'xz-4.999.9_1' then? GL If anyone wants to create a port for svn-export and send it my way for GL review, I would be happy to do that. Otherwise, I expect to have a GL look myself within the next few months. A 'why not', too. (= Thank you. -- Peter Vereshagin pe...@vereshagin.org (http://vereshagin.org) pgp: 1754B9C1 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: svn-export Re: svn bdb checkout?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/16/13 3:55 PM, Peter Vereshagin wrote: Hello. 2013/01/16 15:24:00 -0500 Greg Larkin glar...@freebsd.org = To Peter Vereshagin : GL On 1/16/13 3:07 PM, Peter Vereshagin wrote: GL 2013/01/16 13:51:42 -0600 Joseph A. Nagy, Jr GL jnagyjr1...@gmail.com = To Peter Vereshagin : JANJ On 01/16/13 GL 13:35, Peter Vereshagin wrote: JANJ 2013/01/16 13:19:19 -0600 GL The fsfs and bdb backends refer only to the server side of the GL Subversion repository. Each one represents a different way of storing Ouch! there's the difference that Git made me to forget about, sorry. GL the repository data on the server side and doesn't have any bearing on GL the .svn directory inside of a client-side working copy. GL GL Also note that in earlier versions of the Subversion client, .svn GL directories were created at all levels of the working copy. Since GL 1.7, there is one .svn directory per working copy, but that doesn't GL have anything to do with the backend repository format. Cool. Heard it but was googled into the wrong direction. GL In short, svn export is the way to pull source code out of a GL Subversion repository with the .svn directory. However, that command Will try. Stuck with: $ xz -d svn-export-2012.12.24.1.tar.xz xz: svn-export-2012.12.24.1.tar.xz: File format not recognized Shall I update from 'xz-4.999.9_1' then? I checked it with xz 5.0.0 on a FreeBSD 8.3 machine here, and I could decompress like so: # xz -d -c svn-export-2012.12.24.1.tar.xz | tar tvfB - drwxrwxr-x 0 root root0 Dec 24 12:57 svn-export-2012.12.24.1/ - -rw-rw-r-- 0 root root17972 Dec 24 12:57 svn-export-2012.12.24.1/COPYING drwxrwxr-x 0 root root0 Dec 24 12:57 svn-export-2012.12.24.1/man.md/ - -rw-rw-r-- 0 root root 1350 Dec 24 12:57 svn-export-2012.12.24.1/man.md/svn-export.1.md - -rwxrwxr-x 0 root root 6482 Dec 24 12:57 svn-export-2012.12.24.1/svn-export drwxr-xr-x 0 xyne mx 0 Dec 23 22:48 svn-export-2012.12.24.1/man/ - -rw-r--r-- 0 xyne mx771 Feb 17 2012 svn-export-2012.12.24.1/man/svn-export.1.gz # xz --version xz (XZ Utils) 5.0.0 liblzma 5.0.0 Regards, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlD3HC0ACgkQ0sRouByUApARsQCdGD503bA3t4PFzdsjhsD8UrSE 6I4An0vhcLUNUz86Kj/FNklKPGjEvTNC =xIoS -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: svn-export Re: svn bdb checkout?
Hello.
2013/01/17 00:55:33 +0400 Peter Vereshagin pe...@vereshagin.org = To
freebsd-questions@freebsd.org :
PV GL If anyone wants to create a port for svn-export and send it my way for
PV GL review, I would be happy to do that. Otherwise, I expect to have a
PV GL look myself within the next few months.
PV
PV A 'why not', too. (=
There's a thing about 'svn-export': It requires 'threaded' build of the perl
known to be inappropriate for the production environment (if I'm not mistaken:
this may be obsoltete). At the least this is in the lang/perl5.16/Makefile:
.if defined(WITH_THREADS)
#XXX .if ${ARCH} == amd64
#XXX IGNORE=Threaded perl does not pass tests on ${ARCH}
#XXX .endif
CONFIGURE_ARGS+=-Dusethreads=y
PKGNAMESUFFIX= -threaded
WITH_PTHREAD= yes
# it seems perl malloc has problems with threaded perl on FreeBSD
.undef WITH_PERL_MALLOC
.else
CONFIGURE_ARGS+=-Dusethreads=n
.endif
I believe 'amd64' is the common architecture these days and 'perl malloc' is the
feature needed for profiling and/or leaks detection.
Good news is that such a stuff can be redone with forks instead of threads but
it should take me the time amount I'm not supposed to have of the any early.
By itself perl threading has a fabulously bad luck history, recently
criticized for instance at:
https://speakerdeck.com/stevan_little/perl-is-not-dead-it-is-a-dead-end
Thank you.
--
Peter Vereshagin pe...@vereshagin.org (http://vereshagin.org) pgp: 1754B9C1
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
