RFS: luabind
Dear mentors, I am looking for a sponsor for my package "luabind". * Package name: luabind Version : 0.7 Upstream Author : Daniel Wallin <[EMAIL PROTECTED]>, Arvid Norberg <[EMAIL PROTECTED]> * URL : http://www.rasterbar.com/products/luabind.html * License : MIT, http://www.opensource.org/licenses/mit-license.php Section : libs It builds these binary packages: libluabind-dev - luabind c++ binding for lua: static library and headers libluabind-doc - luabind c++ binding for lua: documentation files libluabind-examples - luabind c++ binding for lua: examples files libluabind0 - luabind c++ binding for lua: runtime library The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/l/luabind - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/l/luabind/luabind_0.7.dsc I would be glad if someone uploaded this package for me. Kind regards Arthur Loiret -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: luabind
On Wed, Apr 04, 2007 at 12:08:55PM +0200, Arthur Loiret wrote: > Dear mentors, > I am looking for a sponsor for my package "luabind". A few comments: * The only available download in the SF.net project website is «luabind-0.7.zip», which is different than your orig (no examples nor documentation, for example). It would be a good idea to explain how did you get it and why (README.Debian?). * In debian/rules:55 there is a `find' that you could probably avoid. Note that dh_fixperms fixes most of the permissions for you already. The only problem is that it doesn't recognize .hpp header files, but that should be fixed in the next version of debhelper (see #404785[1]). In the meantime, you can use a simple chmod. Also, note that the value should be 644 and not 666 (important!). 1. http://bugs.debian.org/404785 * According to the description, it is written towards Lua 5.x, but the package is compiled against 5.0. So, as far as I know, it will not work with Lua 5.1. It would be a good idea to update the description to reflect this issue. It should also be possible to provide packages for both 5.0 and 5.1, but that would require more changes... Is it worth it? * In the changelog, you should use «Closes:»[2] instead of «Close:». 2. http://www.debian.org/doc/debian-policy/footnotes.html#f17 * Upstream's build system is insane and outdated, but it would be even better if you provided your changes as a patch (using quilt, for example) IMHO. > I would be glad if someone uploaded this package for me. I'm sorry, but I'm not a DD ;) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
how pass variables from files for dh_install into rules?
Hello, I tried to use variables in package_name.install file to be read into the /debian/rules , presuming they could be read "as is" and then expanded into rules. But it failed and I had to write directly inside the rules. Is there a way to accomplish this in the file read? Please, examine http://php-java-bridge.cvs.sourceforge.net/php-java-bridge/php-java-bridge/debian/ and send any suggestions about this and other issues you find. It is my first package and first multiple binary packages try. there is not much documentation about this and any suggestion will be welcome. Regards. Andre Felipe Machado http://www.techforce.com.br -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: luabind
Thanks a lot for review :) > * The only available download in the SF.net project website is >«luabind-0.7.zip», which is different than your orig (no examples >nor documentation, for example). It would be a good idea to explain >how did you get it and why (README.Debian?). I download the only aivalable luabind-0.7.zip on sourceforge.net [0], which included examples and documentation, did you get the last update ? 0. http://heanet.dl.sourceforge.net/sourceforge/luabind/ > * In debian/rules:55 there is a `find' that you could probably avoid. >Note that dh_fixperms fixes most of the permissions for you already. >The only problem is that it doesn't recognize .hpp header files, >but that should be fixed in the next version of debhelper (see >#404785[1]). In the meantime, you can use a simple chmod. Also, note >that the value should be 644 and not 666 (important!). Fixed thank you :) > * According to the description, it is written towards Lua 5.x, but the >package is compiled against 5.0. So, as far as I know, it will not >work with Lua 5.1. It would be a good idea to update the description >to reflect this issue. It should also be possible to provide packages >for both 5.0 and 5.1, but that would require more changes... Is it >worth it? I first tried to compile it for lua 5.1, but there were some missing macro, I'm going to try again. > * In the changelog, you should use «Closes:»[2] instead of «Close:». > > 2. http://www.debian.org/doc/debian-policy/footnotes.html#f17 Fixed :) > * Upstream's build system is insane and outdated, but it would be even >better if you provided your changes as a patch (using quilt, for >example) IMHO. I also first tried to patch the orig makefile, but I think a libtool based makefile is a better choice, to generate a dynamic library. Moreover, only 3 short files are required to generate all the build chain, so the diff.gz is still "clean". I think I'm going to send a patch to upstream authors, to propose them this build system for next release. I'm going to add a README.Debian to explain why I've remade the build system and updated examples. > I'm sorry, but I'm not a DD ;) Thanks a lot again :p Thank you for your time, Arthur. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: openjpeg
Hello Romain, Am 2007-03-21 14:25:24, schrieb Romain Beauxis: > More comments: > * You have lintian warnings about missing manpages. They are required so you > may fix this. Ehm, a manpage for a executable is clear, but for a LIB? Thanks, Greetings and nice Day Michelle Konzack Systemadministrator Tamay Dogan Network Debian GNU/Linux Consultant -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSN LinuxMichi 0033/6/6192519367100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Re: RFS: dfu-programmer
Am 2007-03-27 14:13:52, schrieb Andrew Straw: > >The description should probably read "...an USB..." and would ideally > >have a few paragraph breaks. Not using debhelper is fine with me. > A quick google for "a USB" turned up 1.9 million hits and "an USB" > turned up 0.7 million hits. So I'm going to stick with "a USB" unless > you feel strongly about this one. But I added a paragraph break and > hopefully cleaned up the wording a little. "an" is used before a "vowel" like an USB connector an Inode an Error but a Straw(berry) :-) a Maintainer a Debian package Thanks, Greetings and nice Day Michelle Konzack Systemadministrator Tamay Dogan Network Debian GNU/Linux Consultant -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSN LinuxMichi 0033/6/6192519367100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Re: RFS: dfu-programmer
On Wed, Apr 04, 2007 at 08:01:25PM +0200, Michelle Konzack wrote: > Am 2007-03-27 14:13:52, schrieb Andrew Straw: > > >The description should probably read "...an USB..." and would ideally > > >have a few paragraph breaks. Not using debhelper is fine with me. > > A quick google for "a USB" turned up 1.9 million hits and "an USB" > > turned up 0.7 million hits. So I'm going to stick with "a USB" unless > > you feel strongly about this one. But I added a paragraph break and > > hopefully cleaned up the wording a little. > > "an" is used before a "vowel" like > > an USB connector > an Inode > an Error Almost correct. "an" is used if there is a vowel-*sound*. Since U is pronounce alone here (it's an abbreviation, not a word), U is pronounced [ju:]. So it's "an understanding", but "a USB connector". Regards: David -- /) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\ // ~ // Diamond-white roses of fire // \) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost (/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: dfu-programmer
On Wed, 4 Apr 2007 20:01:25 +0200 Michelle Konzack <[EMAIL PROTECTED]> wrote: > "an" is used before a "vowel" like Usually true, but: > an USB connector That just sounds wrong, as a native speaker. Acronyms tend to be variable. In normal, natural, usage, it is 'a USB key' - yet it would also be natural to say 'an ATI drive', 'a SCSI drive', 'an iBook' or 'an iPAQ'. > an Inode > an Error Correct. -- Neil Williams = http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ pgpb06T2iSNJ9.pgp Description: PGP signature
Re: RFS: dfu-programmer
Michelle Konzack wrote: > "an" is used before a "vowel" like > > an USB connector > an Inode > an Error > but > a Straw(berry) :-) > a Maintainer > a Debian package > Well, that's certainly what they taught me at school, too. :) But it's just not what I hear or read living in the US for ~30 years... So I looked a little further: Basically, one says "an" before a _phonemic_ vowel -- in other words, only a vowel that starts with a vowel-like sound. Specifically, this page http://owl.english.purdue.edu/handouts/esl/esliart.html mentions that "u" often does not require an "an", namely when it sounds like "y" in "you". A found a few other references to this on the web, and it appears entirely reasonable and agrees with my personal experience as a native English speaker, so I believe it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: openjpeg
On Wed, Apr 04, 2007 at 08:01:19PM +0200, Michelle Konzack wrote: > Hello Romain, > Am 2007-03-21 14:25:24, schrieb Romain Beauxis: >> More comments: >> * You have lintian warnings about missing manpages. They are required so you >> may fix this. > Ehm, a manpage for a executable is clear, but for a LIB? This was in reference to the programs in openjpeg-tools -- --- Paul "TBBle" Hampson, B.Sc, LPI, MCSE On-hiatus Asian Studies student, ANU The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361) [EMAIL PROTECTED] Of course Pacman didn't influence us as kids. If it did, we'd be running around in darkened rooms, popping pills and listening to repetitive music. -- Kristian Wilson, Nintendo, Inc, 1989 License: http://creativecommons.org/licenses/by/2.1/au/ --- pgpzKu3Cdpmhd.pgp Description: PGP signature
Re: Encoding a manpage in unicode ?
Le Sat, Mar 31, 2007 at 12:14:02PM +0200, Daniel Leidert a écrit : > Am Samstag, den 31.03.2007, 12:35 +0900 schrieb Charles Plessy: > > I wanted to encode some of the manpages I wrote in Unicode, > > but although xsltproc converts them fine, nroff is not able to pipe > > something correct to less, and french accents or chinese characters > > are not correctly displayed. Is there something to do, or is nroff > > simply not unicode compliant? > From what I read (and know), you are converting a DocBook refentry > into groff. Read > file:///usr/share/doc/docbook-xsl-doc-html/doc/manpages/man.charmap.use.subset.html > and use `--param man.charmap.use.subset 0' with xsltproc. This will > replace _all_ unicode characters with their groff code and probably > solve your problem. Hi Daniel, hi Noridata, the man.charmap.use.subset trick worked well for a french accent, I will try later with a han character. Have a nice day, -- Charles Plessy http://charles.plessy.org Wako, Saitama, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
