two sets of html documents
Hello. I'm going to package "The GTK+ Reference Documentation Project" (I'll post ITP to debian-devel soon). The problem I have is that there are two html-trees in gtk-reference -- one for gtk+ and another gdk, two index.html, and I want to put references to both somewhere in http://localhost/doc/HTML/programming/ I could split this package in two and use different `doc-base.package' files for them, but may be there exists more elegant solution? Thanks, -- Alexander Kotelnikov Saint-Petersburg, Russia
Re: update-alternatives
On Wed, Sep 13, 2000 at 10:08:13PM +0200, peter karlsson wrote: > Hi! > > How do I get update-alternatives to keep information when upgrading a > package? > > Currently I have postinst add it and prerm remove it, but if I set the > alternative to point to something else than the default, this means > that that information gets lost everytime I upgrade the package... It doesn't. update-alternatives notices if you have changed the link from the default, and then goes into "manual" mode. Once in manual mode, you need to do "update-alternatives --auto" to revert to auto mode. Until that happens, the sysadmin's choices of alternatives are not affected by any installation or removal of alternatives by maintainer scripts. Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Julian Gilbey, Dept of Maths, QMW, Univ. of London. [EMAIL PROTECTED] Debian GNU/Linux Developer, see http://www.debian.org/~jdg Donate free food to the world's hungry: see http://www.thehungersite.com/
Re: How to sponsor someone and upload a sponsored package?
On Wednesday 13 September 2000, at 17 h 37, the keyboard of Franklin Belew <[EMAIL PROTECTED]> wrote: > I'm not sure if there is a page yet http://www.internatif.org/bortzmeyer/debian/sponsor/ > but the steps are really simple, Here's what you should do if you want to sponsor someone (you must be an official Debian developer) : fill the form below to let us know that you're sponsoring someone download the package produced by the future developer completely check the package and explain all the mistakes to the future developer let him provide a corrected version check it again and upload the package to Incoming if it's ok. For recompiling, assuming you are "Happy Sponsor <[EMAIL PROTECTED]>", use dpkg-buildpackage -rfakeroot -m'Happy Sponsor <[EMAIL PROTECTED]>'. Then, you can simply dupload. speak a bit with the future developer about what he wants to do for Debian and about his motivation. send a mail to [EMAIL PROTECTED] telling them that the candidate successfully packaged XX (which is in Incoming) and that he also wants to do YY for Debian (if he told you something of course !).
how does autoconf find g++?
xxdiff, uses autoconf, which is looking for the C++ compiler. It finds c++ (which is a link into alternatives) and decides it's not g++. The line in configure.in is: AM_CONDITIONAL(IS_COMPILER_GCC, test x$CXX = xg++) Does anybody else, that has packaged a autoconfigured c++ package have a simple way of resolving this? I have thought about: basename `readlink -f \`which c++\`` which first follows all the links and then strips the directories from the path, but this sucks because this makes the build process depend on two additional packages. Since the upstream author would include the Debian stuff upstreams I don't want to make the build process more difficult for non-Debian systems. Any elegant solutions? *t Tomas Pospisek SourcePole - Linux & Open Source Solutions Elestastrasse 18, 7310 Bad Ragaz, Switzerland Tel: +41 (81) 330 77 11
Re: how does autoconf find g++?
On Thu, Sep 14, 2000 at 12:19:28 +0200, T.Pospisek's MailLists wrote: > xxdiff, uses autoconf, which is looking for the C++ compiler. It finds c++ > (which is a link into alternatives) and decides it's not g++. [...] > AM_CONDITIONAL(IS_COMPILER_GCC, test x$CXX = xg++) How about AC_PROG_CXX AM_CONDITIONAL(IS_COMPILER_GCC, test x$GXX = xyes) (Cf. autoconf manual) > Does anybody else, that has packaged a autoconfigured c++ package > have a simple way of resolving this? I have thought about: > basename `readlink -f \`which c++\`` urk... Cheers, Michael -- /~\ ASCII ribbon | * Mechanical Engineering is like looking for a black cat \ / campaign | in a lighted room. X against | * Systems Eng.: looking for a black cat in a dark room / \ HTML mail| in which there is no cat and someone yells "I got it!"
Re: how does autoconf find g++?
On Thu, Sep 14, 2000 at 04:23:29PM +0200, Michael Weber wrote: > On Thu, Sep 14, 2000 at 12:19:28 +0200, T.Pospisek's MailLists wrote: > > xxdiff, uses autoconf, which is looking for the C++ compiler. It finds c++ > > (which is a link into alternatives) and decides it's not g++. > [...] > > AM_CONDITIONAL(IS_COMPILER_GCC, test x$CXX = xg++) > > How about > > AC_PROG_CXX > AM_CONDITIONAL(IS_COMPILER_GCC, test x$GXX = xyes) > > (Cf. autoconf manual) You can also do "CXX=g++ ./configure" -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---'
Re: how does autoconf find g++?
On Thu, 14 Sep 2000, Michael Weber wrote: > How about > > AC_PROG_CXX > AM_CONDITIONAL(IS_COMPILER_GCC, test x$GXX = xyes) > > (Cf. autoconf manual) Wow! Muchas gracias, *t Tomas Pospisek SourcePole - Linux & Open Source Solutions Elestastrasse 18, 7310 Bad Ragaz, Switzerland Tel: +41 (81) 330 77 11
Sponsor's responsibilities
How exacting should a sponsor be? A sponsor was reamed on a list a while back because he duploaded a package with a fairly minor error. He'd identified the problem and told the packager to fix it in the next version and said that this was his impression of what a sponsor should do. That is, get the package lintian clean, make sure the package does no intentional or inadvertent damage, md5sum the tarball against upstream and so on. But let the packager make his own little mistakes and fix them himself. This happened to me when I was first sponsored. I missed the debhelper build-depends that my Standards-Version required. But lots of old-time developers are getting caught by this as they upgrade their packages. Anyhow, ignore this specific example. I just mean in the general case. Get it close or flog the package until it squeaks? Rick --
Re: Sponsor's responsibilities
On 2914T102042-0700, Rick Younie wrote: > Anyhow, ignore this specific example. I just mean in the general > case. Get it close or flog the package until it squeaks? Well, in the final analysis, it's the sponsor's neck on the line if something bad happens. It's a matter of how much he trusts the sponsee. Personally, I'd use the same standard I use on my own packages. -- %%% Antti-Juhani Kaijanaho % [EMAIL PROTECTED] % http://www.iki.fi/gaia/ %%%
Re: update-alternatives
On Wed, Sep 13, 2000 at 10:08:13PM +0200, peter karlsson wrote: > Hi! > > How do I get update-alternatives to keep information when upgrading a > package? > > Currently I have postinst add it and prerm remove it, but if I set the > alternative to point to something else than the default, this means > that that information gets lost everytime I upgrade the package... It doesn't. update-alternatives notices if you have changed the link from the default, and then goes into "manual" mode. Once in manual mode, you need to do "update-alternatives --auto" to revert to auto mode. Until that happens, the sysadmin's choices of alternatives are not affected by any installation or removal of alternatives by maintainer scripts. Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Julian Gilbey, Dept of Maths, QMW, Univ. of London. [EMAIL PROTECTED] Debian GNU/Linux Developer, see http://www.debian.org/~jdg Donate free food to the world's hungry: see http://www.thehungersite.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to sponsor someone and upload a sponsored package?
On Wednesday 13 September 2000, at 17 h 37, the keyboard of Franklin Belew <[EMAIL PROTECTED]> wrote: > I'm not sure if there is a page yet http://www.internatif.org/bortzmeyer/debian/sponsor/ > but the steps are really simple, Here's what you should do if you want to sponsor someone (you must be an official Debian developer) : fill the form below to let us know that you're sponsoring someone download the package produced by the future developer completely check the package and explain all the mistakes to the future developer let him provide a corrected version check it again and upload the package to Incoming if it's ok. For recompiling, assuming you are "Happy Sponsor <[EMAIL PROTECTED]>", use dpkg-buildpackage -rfakeroot -m'Happy Sponsor <[EMAIL PROTECTED]>'. Then, you can simply dupload. speak a bit with the future developer about what he wants to do for Debian and about his motivation. send a mail to [EMAIL PROTECTED] telling them that the candidate successfully packaged XX (which is in Incoming) and that he also wants to do YY for Debian (if he told you something of course !). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
how does autoconf find g++?
xxdiff, uses autoconf, which is looking for the C++ compiler. It finds c++ (which is a link into alternatives) and decides it's not g++. The line in configure.in is: AM_CONDITIONAL(IS_COMPILER_GCC, test x$CXX = xg++) Does anybody else, that has packaged a autoconfigured c++ package have a simple way of resolving this? I have thought about: basename `readlink -f \`which c++\`` which first follows all the links and then strips the directories from the path, but this sucks because this makes the build process depend on two additional packages. Since the upstream author would include the Debian stuff upstreams I don't want to make the build process more difficult for non-Debian systems. Any elegant solutions? *t Tomas Pospisek SourcePole - Linux & Open Source Solutions Elestastrasse 18, 7310 Bad Ragaz, Switzerland Tel: +41 (81) 330 77 11 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: how does autoconf find g++?
On Thu, Sep 14, 2000 at 12:19:28 +0200, T.Pospisek's MailLists wrote: > xxdiff, uses autoconf, which is looking for the C++ compiler. It finds c++ > (which is a link into alternatives) and decides it's not g++. [...] > AM_CONDITIONAL(IS_COMPILER_GCC, test x$CXX = xg++) How about AC_PROG_CXX AM_CONDITIONAL(IS_COMPILER_GCC, test x$GXX = xyes) (Cf. autoconf manual) > Does anybody else, that has packaged a autoconfigured c++ package > have a simple way of resolving this? I have thought about: > basename `readlink -f \`which c++\`` urk... Cheers, Michael -- /~\ ASCII ribbon | * Mechanical Engineering is like looking for a black cat \ / campaign | in a lighted room. X against | * Systems Eng.: looking for a black cat in a dark room / \ HTML mail| in which there is no cat and someone yells "I got it!" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: how does autoconf find g++?
On Thu, Sep 14, 2000 at 04:23:29PM +0200, Michael Weber wrote: > On Thu, Sep 14, 2000 at 12:19:28 +0200, T.Pospisek's MailLists wrote: > > xxdiff, uses autoconf, which is looking for the C++ compiler. It finds c++ > > (which is a link into alternatives) and decides it's not g++. > [...] > > AM_CONDITIONAL(IS_COMPILER_GCC, test x$CXX = xg++) > > How about > > AC_PROG_CXX > AM_CONDITIONAL(IS_COMPILER_GCC, test x$GXX = xyes) > > (Cf. autoconf manual) You can also do "CXX=g++ ./configure" -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: how does autoconf find g++?
On Thu, 14 Sep 2000, Michael Weber wrote: > How about > > AC_PROG_CXX > AM_CONDITIONAL(IS_COMPILER_GCC, test x$GXX = xyes) > > (Cf. autoconf manual) Wow! Muchas gracias, *t Tomas Pospisek SourcePole - Linux & Open Source Solutions Elestastrasse 18, 7310 Bad Ragaz, Switzerland Tel: +41 (81) 330 77 11 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Sponsor's responsibilities
How exacting should a sponsor be? A sponsor was reamed on a list a while back because he duploaded a package with a fairly minor error. He'd identified the problem and told the packager to fix it in the next version and said that this was his impression of what a sponsor should do. That is, get the package lintian clean, make sure the package does no intentional or inadvertent damage, md5sum the tarball against upstream and so on. But let the packager make his own little mistakes and fix them himself. This happened to me when I was first sponsored. I missed the debhelper build-depends that my Standards-Version required. But lots of old-time developers are getting caught by this as they upgrade their packages. Anyhow, ignore this specific example. I just mean in the general case. Get it close or flog the package until it squeaks? Rick -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sponsor's responsibilities
On 2914T102042-0700, Rick Younie wrote: > Anyhow, ignore this specific example. I just mean in the general > case. Get it close or flog the package until it squeaks? Well, in the final analysis, it's the sponsor's neck on the line if something bad happens. It's a matter of how much he trusts the sponsee. Personally, I'd use the same standard I use on my own packages. -- %%% Antti-Juhani Kaijanaho % [EMAIL PROTECTED] % http://www.iki.fi/gaia/ %%% -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
two sets of html documents
Hello. I'm going to package "The GTK+ Reference Documentation Project" (I'll post ITP to debian-devel soon). The problem I have is that there are two html-trees in gtk-reference -- one for gtk+ and another gdk, two index.html, and I want to put references to both somewhere in http://localhost/doc/HTML/programming/ I could split this package in two and use different `doc-base.package' files for them, but may be there exists more elegant solution? Thanks, -- Alexander Kotelnikov Saint-Petersburg, Russia -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
