Xlibs or Xlib6
First I don't know why previous Changelogs has been removed: http://http.us.debian.org/debian/dists/Debian2.2r4/ChangeLog (works fine) http://http.us.debian.org/debian/dists/Debian2.2r3/ChangeLog (does not work) ... One of my package build machines both have: dpkg -s xlibs and dpkg -s xlib6 shlibdebs chooses xlibs, but it seems newer distribs does not have xlibs? http://packages.debian.org/stable/allpackages.html I'm trying to support both old and new Debian Distributions. As I'm unsure where to find information about previous releases, do any of you have a suggestion or conclusion? -- Christian A. Westgaard Software Developer ++ Linux Team Opera Software ASA Web site : http://www.opera.com E-mail : [EMAIL PROTECTED] Direct : +47 24 16 42 08 Phone : +47 24 16 40 00 Fax : +47 24 16 40 02 Copyright Opera Software - © All rights reserved. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Xlibs or Xlib6
2.2 never had xlibs, just xlib6g (libc6 version) and xlib6 (libc5 version)... xlibs is newto woody/sid. I have both xlibs-dev and xlib6g-dev on my sid machine, and build lotsa packages w/X support, and xlibs is what's put in my substvars as generated by dpkg-shlibdeps -- xlib6g{,-dev} are just empty packages to smooth upgrades in woody and sid. Hence, no libraries inside and certainly no shlibs file. For multiple distro support, hypothetically you should just need Build-Depends: xlibs-dev | xlib6g-dev for things to work. On Mon, Dec 03, 2001 at 09:53:03AM +0100, Christian Westgaard wrote: > First I don't know why previous Changelogs has been removed: > http://http.us.debian.org/debian/dists/Debian2.2r4/ChangeLog (works fine) > http://http.us.debian.org/debian/dists/Debian2.2r3/ChangeLog (does not work) > ... > > One of my package build machines both have: > dpkg -s xlibs > and > dpkg -s xlib6 > > > shlibdebs chooses xlibs, but it seems newer distribs does not have xlibs? > http://packages.debian.org/stable/allpackages.html > > I'm trying to support both old and new Debian Distributions. > > As I'm unsure where to find information about previous releases, > do any of you have a suggestion or conclusion? -- Mike Markley <[EMAIL PROTECTED]> GPG: 0x3B047084 7FC7 0DC0 EF31 DF83 7313 FE2B 77A8 F36A 3B04 7084 To YOU I'm an atheist; to God, I'm the Loyal Opposition. - Woody Allen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-reconfigure, policy, and least surprise principle
* Roland Mas | A hypothetical third hand would be holding this: the postinst first | reads the master config file and shoves its values into Debconf, then | asks the debconf questions, then updates the sourceforge.conf file | with the new values from Debconf. It sounds horribly messy, though, | and I'm not sure it's doable without too much hackery. This is the right way, though. Note that unless the admin has asked for it, previously answered debconf questions won't be asked again, so you wouldn't bother the admin too much. Look at suck or mailman for examples on how to do this. -- Tollef Fog Heen Axiom #1: You Can't Win -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
dh_clean issues
I am experiencing trouble packaging some of the applicactions developed at work. Using dh_clean (or dh_clean -[d|k]) in my rules file removes some .orig files that are legitimate and needed. Changing file names would involve changing code, and it's not a wellcome idea ;-) It is also giving trouble with CVS operations... Any hint, suggestion, creative criticism and the such is more than wellcome. [Cc:ing me will be greatly appreciated, as I am not suscribed from this email address, at work]. -- Próxima estación, Esperanza. Final de trayecto - Metro de Madrid Amaya Rodrigo Sastrewww.andago.com Sta Engracia, 54 28010 Madrid BOFH-dev && CVS Evangelist Tfno: 912041124 Fax: 91204 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dh_clean issues
On Mon, Dec 03, 2001 at 01:07:13PM +0100, Amaya wrote: > Using dh_clean (or dh_clean -[d|k]) in my rules file removes some .orig > files that are legitimate and needed. Changing file names would involve > changing code, and it's not a wellcome idea ;-) dh_clean(1) says: -Xitem --exclude=item Exclude files that contain "item" anywhere in their filename from being deleted, even if they would nor mally be deleted. You may use this option multiple times to build up a list of things to exclude. -- Colin Watson [[EMAIL PROTECTED]] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dh_clean issues
Colin Watson dijo: > dh_clean(1) says: >-Xitem --exclude=item Oh, well, I missed it, it's no good to be all upset and in a hurry :-) Thanks! -- Próxima estación, Esperanza. Final de trayecto - Metro de Madrid Amaya Rodrigo Sastrewww.andago.com Sta Engracia, 54 28010 Madrid BOFH-dev && CVS Evangelist Tfno: 912041124 Fax: 91204 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-reconfigure, policy, and least surprise principle
On Sun, Dec 02, 2001 at 12:36:26PM +0100, Tollef Fog Heen wrote: > * Roland Mas > | A hypothetical third hand would be holding this: the postinst first > | reads the master config file and shoves its values into Debconf, then > This is the right way, though. Note that unless the admin has asked > for it, previously answered debconf questions won't be asked again, > so you wouldn't bother the admin too much. I've done this in one of my packages too but I worry what will happen when Debconf finally gets support for remote databases. At that point the configuration on the system where the configuration front end is running may not be the configuration of the system that is being configured. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." msg04895/pgp0.pgp Description: PGP signature
why did the ocaml package not enter woody ?
Hello, ... I maintain the ocaml package, and am wondering if there is any way to check why the ocaml package has not entered woody/testing. It has been build since november 10 on all 8 architectures going to be released with woody, and there is no bug (apart a very old wishlist bug which i will grant after woody is releaseD). Now, the current version of ocaml in woody (3.01-6.1) is old there have been 3.02 package for a long time. The result of this is that the lablgtk package, which depends on lablgl and ocaml is not present in woody, which is _not_ a nice thing. Also the current version of both lablgl and lablgtk in unstable are incompatible with 3.01. Please someone point me to the right place to bring this kind of problems. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Xlibs or Xlib6
On Mon, Dec 03, 2001 at 09:53:03AM +0100, Christian Westgaard wrote: > First I don't know why previous Changelogs has been removed: > http://http.us.debian.org/debian/dists/Debian2.2r4/ChangeLog (works fine) > http://http.us.debian.org/debian/dists/Debian2.2r3/ChangeLog (does not work) > ... It isn't removed, it's included in the newest changelog. The symlink "Debian2.2r3", on the other hand, is removed, because it would be redundant. > One of my package build machines both have: > dpkg -s xlibs > and > dpkg -s xlib6 > > shlibdebs chooses xlibs, but it seems newer distribs does not have xlibs? > http://packages.debian.org/stable/allpackages.html > > I'm trying to support both old and new Debian Distributions. The xlib6 package is compiled against libc5, AFAIR, so this would mean you would be supporting _very_ old Debian distributions :) I think you want the xlib6g package, that's the good one from potato (latest stable Debian). -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: multiple tcl/tk -dev versions ???
On Thu, Nov 22, 2001 at 08:12:58PM -0500, Matt Zimmerman wrote: > On Thu, Nov 22, 2001 at 09:47:28AM +0100, Sven wrote: > > > I have a package that i make build-depend on tcl/tk-dev 8.3, but the configure > > process will check for the tcl/tk presence, and get one if available. > > > > It will check for various other versions before 8.3. > > Change the configure script to look for 8.3 first, or to allow the user to > specify a specific version (via a --with flag) and use that. Ok, thanks, will do that, once the current version has moved into testing, ... Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
40만원에 펜티엄4+17"평면 모니터를 드립니다!
Title: ÆæÆ¼¾ö4+17"¿ÏÀüÆò¸é ¸ð´ÏÅͰ¡ 40¸¸¿ø... ÄÄÇ»ÅÍ °¡°ÝÀÇ Çõ¸í... ÄÄÇ»ÅÍÀÇ °¡°Ý... ÀÌÁ¨ ´õ ÀÌ»ó ºñ½Î°Ô ÁöºÒµÇ¾îÁ®¼± ¾ÈµË´Ï´Ù.24°³¿ù µ¿¾È Àǹ«¼îÇθ¸ ÇØÁֽøé 40¸¸¿ø¿¡ ÆæÆ¼¾ö4 1.5G+17" ¿ÏÀüÆò¸é ¸ð´ÏÅ͸¦ µå¸³´Ï´Ù.ÃֽŠÄÄÇ»Å͸¦ 40¸¸¿ø¿¡ ±¸¸ÅÇÒ ¼ö ÀÖ´Â ÀýÈ£ÀÇ Âù½º!!À̹ø À̺¥Æ®¸¦ ³õÄ¡Áö ¸¶¼¼¿ä... ÄÄÇ»ÅÍ ±âº»Á¤º¸ ¡íÇÁ·Î¼¼¼ : Pentium 4 1.5Ghz¡í¸Þ¸ð¸® : 256Mbyte ¡íÇϵå : 40Gbyte ¡íCD·Ò : »ï¼º52X¡í¸ð´ÏÅÍ(Æ÷ÇÔ) : ´ë¿ì17" ¿ÏÀüÆò¸é(ÀÚ¼¼ÇÑ ³»¿ëÀº ȨÆäÀÌÁö¿¡¼ È®ÀÎÇÏ¿© Áֽʽÿä) À̺¥Æ® ¼Ó, ¶ÇÇϳªÀÇ À̺¥Æ®.. ÁÖÀ§ºÐµéÀ» ¼Ò°³ÇÏ¿© ÄÄÇ»Å͸¦ ±¸¸ÅÇÏ°Ô ÇÏ½Ã¸é ±¤°íÆÇ¸Åºñ 5¸¸¿øÀ» µå¸³´Ï´Ù. ¾ÆÅäÁîÇǾƴÂ... ÃÖ÷´Ü ¸¶ÄÉÆÃ½Ã½ºÅÛÀ¸·Î ¸ÖƼ¹Ìµð¾î ¼¼»óÀ» ¿¾î°¡´Â (ÁÖ)¾ÆÅäÁîÇǾƴ ÃÖ÷´Ü ¸¶ÄÉÆÃ±â¹ýÀ¸·Î ¹à°í °ÇÀüÇÏ°Ô ¼ºÀåÇØ °¡´Â ±â¾÷ÀÔ´Ï´Ù. ¹Ù·Î°¡±â ȨÆäÀÌÁö GO ¡íÇã¶ô¾øÀÌ ¸ÞÀÏÀ» µå·Á Á˼ÛÇÕ´Ï´Ù.¡í±ÍÇÏÀÇ ¸ÞÀÏÁÖ¼Ò´Â ÀÎÅͳݻó °Ô½ÃÆÇµî¿¡¼ º¸¾Æ ¾Ë°ÔµÇ¾úÀ»»Ó ´Ù¸¥ ¾î¶°ÇÑ ºÒ¹ýÀûÀÎ °æ·Î·Î ¾Ë °Ô µÈ °ÍÀÌ ¾Æ´Ï¹Ç·Î ¾È½ÉÇϼŵµ ÁÁ½À´Ï´Ù.¡í±ÍÇÏÀÇ À̸ÞÀÏÁÖ¼ÒÀÎ [EMAIL PROTECTED]À¸·Î Àý´ë µÎ ¹ø ¹ß¼ÛµÇÁö ¾Ê½À´Ï´Ù.¡í¼ö½ÅÀ» ¿øÄ¡ ¾ÊÀ¸½Ã¸é ¿©±â¸¦ Ŭ¸¯ÇÏ¿©Áֽʽÿä.
tcl/tk8 or greater
Hi there yal, If a program I am packing depends on tcl/tk8 or newer, which packages should I get it to depend on, as there being multiple 'tcl8.*/tk8.*'s? Thanks, Hereward -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Packaging CVS snapshots?
Carlos Laviola dijo: > Some folks at #debian-devel suggested me to use dbs, Sorry, what do you exactly mean by dbs? > Can anyone give me some clues, or could anyone that does/has done this > give me a hand? What is exactly what you are having trouble with? Automating? Dealing with CVS stuff? I am also very interested on this subject, but have limited experience. Just `cvs export` or `cvs-buildpackage` so far :-) [Probably should be getting more sleep and not being so inquisitive ;-)] -- .''`. El dolor, cuando no se convierte en verdugo, es un gran maestro. : :' :-- Concepción Arenal. `. `' Proudly running Debian GNU/Linux Sid (Kernel 2.4.9) `-www.amayita.com www.malapecora.com www.chicasduras.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: tcl/tk8 or greater
As the Tcl/Tk maintainer, I'd prefer you depend on 8.3... now, if it's a script, then depending on tcl8.3 | tclsh is fine (tclsh is a virtual package). For linking, though, please use 8.3. On Mon, Dec 03, 2001 at 08:11:15PM +, Hereward Cooper wrote: > Hi there yal, > > If a program I am packing depends on tcl/tk8 or newer, which packages should I > get it to depend on, as there being multiple 'tcl8.*/tk8.*'s? > > Thanks, > > Hereward > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- Mike Markley <[EMAIL PROTECTED]> GPG: 0x3B047084 7FC7 0DC0 EF31 DF83 7313 FE2B 77A8 F36A 3B04 7084 Actual war is a very messy business. Very, very messy business. - Kirk, "A Taste of Armageddon", stardate 3193.0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
libtool, c++ and SO-names
Hello, I am still trying to package mpqc and it's library libsc. The last major problem is with SO-names for the shared libraries. Upstream didn't use SO-names yet, but is willing to do now. However, he said: > The problem is that C++ is not binary compatible across different > compiler vendors or even compiler versions. C++ optimizations end up > coupling the private interface and public interface. Say libsc4_2.0.3 > was released and I only changed manual pages in 2.0.4. If I decided to > switch from gcc 2.96 to gcc 3.0 in the 2.0.4 release, then I would have > to release libsc5_2.0.4. Thus, to SO_NAME is coupled to both source and > package issues. and earlier: > The problem with C++ is that it is very difficult to make any change > without introducing binary incompatibilities due to possible changes > in inline functions, virtual table layout, and data layout. Even > building the new package with a newer version of the compiler or std > library could cause problems. So, for example, 2.0.1 might be binary > incompatible with 2.0.0, in fact, it probably would be incompatible. The libtool-manual says about c++-libraries: > Creating libraries of C++ code should be a fairly straightforward > process, because its object files differ from C ones in only three > ways: > 1. Because of name mangling, C++ libraries are only usable by the > C++ compiler that created them. This decision was made by the > designers of C++ in order to protect users from conflicting > implementations of features such as constructors, exception > handling, and RTTI. Does this mean I have to put a Depends: g++(= $MY_G++) into libsc-dev's depends? > 2. On some systems, the C++ compiler must take special actions for > the dynamic linker to run dynamic (i.e., run-time) initializers. > This means that we should not call `ld' directly to link such > libraries, and we should use the C++ compiler instead. Is Linux a 'some system'? > 3. C++ compilers will link some Standard C++ library in by default, > but libtool does not know which are these libraries, so it cannot > even run the inter-library dependence analyzer to check how to link > it in. Therefore, running `ld' to link a C++ program or library is > deemed to fail. However, running the C++ compiler directly may lead > to problems related with inter-library dependencies. What does that mean? > The conclusion is that libtool is not ready for general use for C++ > libraries. (Sorry for the longish quotes) So, can anybody point me to documentation on how to handle this, e.g. other c++-libraries who do it 'the right way'? Should I refrain from shipping (shared) libraries? What would happen if I change my c++-compiler but upstream doesn't? Would that mean that SO-names would be out of sync? Is everything easy and changing SO-names is really only needed for interface changes? If so, what does one have to consider? thanks for any hints, Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Packaging CVS snapshots?
On Mon, Dec 03, 2001 at 11:15:49PM +0100, Amaya wrote: > Carlos Laviola dijo: > > Some folks at #debian-devel suggested me to use dbs, > > Sorry, what do you exactly mean by dbs? The 'dbs' package :-) > > Can anyone give me some clues, or could anyone that does/has done this > > give me a hand? > > What is exactly what you are having trouble with? > Automating? Dealing with CVS stuff? Yes, I would like to know of an easy way to release frequent (weekly, quarterly, monthly) Debian packages of CVS snapshots of certain software like lopster and licq. > I am also very interested on this subject, but have limited experience. > Just `cvs export` or `cvs-buildpackage` so far :-) That would be cool if one wanted to maintain a CVS repository of his own with his Debian packages, I guess. No? I'm afraid what I want to do here is different... > [Probably should be getting more sleep and not being so inquisitive ;-)] We all need to, apparently :)) -- _ _ _| _ _ | _ . _ | _ to hell with icq, use jabber! (_(_|| |(_)_) |(_|\/|(_)|(_| THIS SPACE INTENTIONALLY LEFT BLANK? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Packaging CVS snapshots?
On Mon, Dec 03, 2001 at 11:56:57PM -0200, Carlos Laviola wrote: > On Mon, Dec 03, 2001 at 11:15:49PM +0100, Amaya wrote: > > Carlos Laviola dijo: > > > Some folks at #debian-devel suggested me to use dbs, > > > > Sorry, what do you exactly mean by dbs? > > The 'dbs' package :-) > > > > Can anyone give me some clues, or could anyone that does/has done this > > > give me a hand? > > > > What is exactly what you are having trouble with? > > Automating? Dealing with CVS stuff? > > Yes, I would like to know of an easy way to release frequent (weekly, > quarterly, monthly) Debian packages of CVS snapshots of certain > software like lopster and licq. > My AM suggested that it is really quite easy to merely apply the debian directory to a cvs export rather that using the ever-so-complicated (and "evil") dbs. Supposedly (I'm maybe wrong here) dbs does not give a clean .orig.tar.gz (which is a bad thing) -- Duncan Findlay -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Xlibs or Xlib6
First I don't know why previous Changelogs has been removed: http://http.us.debian.org/debian/dists/Debian2.2r4/ChangeLog (works fine) http://http.us.debian.org/debian/dists/Debian2.2r3/ChangeLog (does not work) ... One of my package build machines both have: dpkg -s xlibs and dpkg -s xlib6 shlibdebs chooses xlibs, but it seems newer distribs does not have xlibs? http://packages.debian.org/stable/allpackages.html I'm trying to support both old and new Debian Distributions. As I'm unsure where to find information about previous releases, do any of you have a suggestion or conclusion? -- Christian A. Westgaard Software Developer ++ Linux Team Opera Software ASA Web site : http://www.opera.com E-mail : [EMAIL PROTECTED] Direct : +47 24 16 42 08 Phone : +47 24 16 40 00 Fax : +47 24 16 40 02 Copyright Opera Software - © All rights reserved.
Re: Xlibs or Xlib6
2.2 never had xlibs, just xlib6g (libc6 version) and xlib6 (libc5 version)... xlibs is newto woody/sid. I have both xlibs-dev and xlib6g-dev on my sid machine, and build lotsa packages w/X support, and xlibs is what's put in my substvars as generated by dpkg-shlibdeps -- xlib6g{,-dev} are just empty packages to smooth upgrades in woody and sid. Hence, no libraries inside and certainly no shlibs file. For multiple distro support, hypothetically you should just need Build-Depends: xlibs-dev | xlib6g-dev for things to work. On Mon, Dec 03, 2001 at 09:53:03AM +0100, Christian Westgaard wrote: > First I don't know why previous Changelogs has been removed: > http://http.us.debian.org/debian/dists/Debian2.2r4/ChangeLog (works fine) > http://http.us.debian.org/debian/dists/Debian2.2r3/ChangeLog (does not work) > ... > > One of my package build machines both have: > dpkg -s xlibs > and > dpkg -s xlib6 > > > shlibdebs chooses xlibs, but it seems newer distribs does not have xlibs? > http://packages.debian.org/stable/allpackages.html > > I'm trying to support both old and new Debian Distributions. > > As I'm unsure where to find information about previous releases, > do any of you have a suggestion or conclusion? -- Mike Markley <[EMAIL PROTECTED]> GPG: 0x3B047084 7FC7 0DC0 EF31 DF83 7313 FE2B 77A8 F36A 3B04 7084 To YOU I'm an atheist; to God, I'm the Loyal Opposition. - Woody Allen
Re: dpkg-reconfigure, policy, and least surprise principle
* Roland Mas | A hypothetical third hand would be holding this: the postinst first | reads the master config file and shoves its values into Debconf, then | asks the debconf questions, then updates the sourceforge.conf file | with the new values from Debconf. It sounds horribly messy, though, | and I'm not sure it's doable without too much hackery. This is the right way, though. Note that unless the admin has asked for it, previously answered debconf questions won't be asked again, so you wouldn't bother the admin too much. Look at suck or mailman for examples on how to do this. -- Tollef Fog Heen Axiom #1: You Can't Win
dh_clean issues
I am experiencing trouble packaging some of the applicactions developed at work. Using dh_clean (or dh_clean -[d|k]) in my rules file removes some .orig files that are legitimate and needed. Changing file names would involve changing code, and it's not a wellcome idea ;-) It is also giving trouble with CVS operations... Any hint, suggestion, creative criticism and the such is more than wellcome. [Cc:ing me will be greatly appreciated, as I am not suscribed from this email address, at work]. -- Próxima estación, Esperanza. Final de trayecto - Metro de Madrid Amaya Rodrigo Sastrewww.andago.com Sta Engracia, 54 28010 Madrid BOFH-dev && CVS Evangelist Tfno: 912041124 Fax: 91204
Re: dh_clean issues
On Mon, Dec 03, 2001 at 01:07:13PM +0100, Amaya wrote: > Using dh_clean (or dh_clean -[d|k]) in my rules file removes some .orig > files that are legitimate and needed. Changing file names would involve > changing code, and it's not a wellcome idea ;-) dh_clean(1) says: -Xitem --exclude=item Exclude files that contain "item" anywhere in their filename from being deleted, even if they would nor mally be deleted. You may use this option multiple times to build up a list of things to exclude. -- Colin Watson [EMAIL PROTECTED]
Re: dh_clean issues
Colin Watson dijo: > dh_clean(1) says: >-Xitem --exclude=item Oh, well, I missed it, it's no good to be all upset and in a hurry :-) Thanks! -- Próxima estación, Esperanza. Final de trayecto - Metro de Madrid Amaya Rodrigo Sastrewww.andago.com Sta Engracia, 54 28010 Madrid BOFH-dev && CVS Evangelist Tfno: 912041124 Fax: 91204
Re: dpkg-reconfigure, policy, and least surprise principle
On Sun, Dec 02, 2001 at 12:36:26PM +0100, Tollef Fog Heen wrote: > * Roland Mas > | A hypothetical third hand would be holding this: the postinst first > | reads the master config file and shoves its values into Debconf, then > This is the right way, though. Note that unless the admin has asked > for it, previously answered debconf questions won't be asked again, > so you wouldn't bother the admin too much. I've done this in one of my packages too but I worry what will happen when Debconf finally gets support for remote databases. At that point the configuration on the system where the configuration front end is running may not be the configuration of the system that is being configured. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgpuyuizP56PN.pgp Description: PGP signature
why did the ocaml package not enter woody ?
Hello, ... I maintain the ocaml package, and am wondering if there is any way to check why the ocaml package has not entered woody/testing. It has been build since november 10 on all 8 architectures going to be released with woody, and there is no bug (apart a very old wishlist bug which i will grant after woody is releaseD). Now, the current version of ocaml in woody (3.01-6.1) is old there have been 3.02 package for a long time. The result of this is that the lablgtk package, which depends on lablgl and ocaml is not present in woody, which is _not_ a nice thing. Also the current version of both lablgl and lablgtk in unstable are incompatible with 3.01. Please someone point me to the right place to bring this kind of problems. Friendly, Sven Luther
Re: Xlibs or Xlib6
On Mon, Dec 03, 2001 at 09:53:03AM +0100, Christian Westgaard wrote: > First I don't know why previous Changelogs has been removed: > http://http.us.debian.org/debian/dists/Debian2.2r4/ChangeLog (works fine) > http://http.us.debian.org/debian/dists/Debian2.2r3/ChangeLog (does not work) > ... It isn't removed, it's included in the newest changelog. The symlink "Debian2.2r3", on the other hand, is removed, because it would be redundant. > One of my package build machines both have: > dpkg -s xlibs > and > dpkg -s xlib6 > > shlibdebs chooses xlibs, but it seems newer distribs does not have xlibs? > http://packages.debian.org/stable/allpackages.html > > I'm trying to support both old and new Debian Distributions. The xlib6 package is compiled against libc5, AFAIR, so this would mean you would be supporting _very_ old Debian distributions :) I think you want the xlib6g package, that's the good one from potato (latest stable Debian). -- 2. That which causes joy or happiness.
Re: multiple tcl/tk -dev versions ???
On Thu, Nov 22, 2001 at 08:12:58PM -0500, Matt Zimmerman wrote: > On Thu, Nov 22, 2001 at 09:47:28AM +0100, Sven wrote: > > > I have a package that i make build-depend on tcl/tk-dev 8.3, but the > > configure > > process will check for the tcl/tk presence, and get one if available. > > > > It will check for various other versions before 8.3. > > Change the configure script to look for 8.3 first, or to allow the user to > specify a specific version (via a --with flag) and use that. Ok, thanks, will do that, once the current version has moved into testing, ... Friendly, Sven Luther
40만원에 펜티엄4+17"평면 모니터를 드립니다!
Title: 펜티엄4+17"완전평면 모니터가 40만원... 컴퓨터 가격의 혁명... 컴퓨터의 가격... 이젠 더 이상 비싸게 지불되어져선 안됩니다.24개월 동안 의무쇼핑만 해주시면 40만원에 펜티엄4 1.5G+17" 완전평면 모니터를 드립니다.최신 컴퓨터를 40만원에 구매할 수 있는 절호의 찬스!!이번 이벤트를 놓치지 마세요... 컴퓨터 기본정보 ≫프로세서 : Pentium 4 1.5Ghz≫메모리 : 256Mbyte ≫하드 : 40Gbyte ≫CD롬 : 삼성52X≫모니터(포함) : 대우17" 완전평면(자세한 내용은 홈페이지에서 확인하여 주십시요) 이벤트 속, 또하나의 이벤트.. 주위분들을 소개하여 컴퓨터를 구매하게 하시면 광고판매비 5만원을 드립니다. 아토즈피아는... 최첨단 마케팅시스템으로 멀티미디어 세상을 열어가는 (주)아토즈피아는 최첨단 마케팅기법으로 밝고 건전하게 성장해 가는 기업입니다. 바로가기 홈페이지 GO ≫허락없이 메일을 드려 죄송합니다.≫귀하의 메일주소는 인터넷상 게시판등에서 보아 알게되었을뿐 다른 어떠한 불법적인 경로로 알 게 된 것이 아니므로 안심하셔도 좋습니다.≫귀하의 이메일주소인 [EMAIL PROTECTED] 절대 두 번 발송되지 않습니다.≫수신을 원치 않으시면 여기를 클릭하여주십시요.
tcl/tk8 or greater
Hi there yal, If a program I am packing depends on tcl/tk8 or newer, which packages should I get it to depend on, as there being multiple 'tcl8.*/tk8.*'s? Thanks, Hereward
Re: Packaging CVS snapshots?
Carlos Laviola dijo: > Some folks at #debian-devel suggested me to use dbs, Sorry, what do you exactly mean by dbs? > Can anyone give me some clues, or could anyone that does/has done this > give me a hand? What is exactly what you are having trouble with? Automating? Dealing with CVS stuff? I am also very interested on this subject, but have limited experience. Just `cvs export` or `cvs-buildpackage` so far :-) [Probably should be getting more sleep and not being so inquisitive ;-)] -- .''`. El dolor, cuando no se convierte en verdugo, es un gran maestro. : :' :-- Concepción Arenal. `. `' Proudly running Debian GNU/Linux Sid (Kernel 2.4.9) `-www.amayita.com www.malapecora.com www.chicasduras.com
Re: tcl/tk8 or greater
As the Tcl/Tk maintainer, I'd prefer you depend on 8.3... now, if it's a script, then depending on tcl8.3 | tclsh is fine (tclsh is a virtual package). For linking, though, please use 8.3. On Mon, Dec 03, 2001 at 08:11:15PM +, Hereward Cooper wrote: > Hi there yal, > > If a program I am packing depends on tcl/tk8 or newer, which packages should I > get it to depend on, as there being multiple 'tcl8.*/tk8.*'s? > > Thanks, > > Hereward > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- Mike Markley <[EMAIL PROTECTED]> GPG: 0x3B047084 7FC7 0DC0 EF31 DF83 7313 FE2B 77A8 F36A 3B04 7084 Actual war is a very messy business. Very, very messy business. - Kirk, "A Taste of Armageddon", stardate 3193.0
libtool, c++ and SO-names
Hello, I am still trying to package mpqc and it's library libsc. The last major problem is with SO-names for the shared libraries. Upstream didn't use SO-names yet, but is willing to do now. However, he said: > The problem is that C++ is not binary compatible across different > compiler vendors or even compiler versions. C++ optimizations end up > coupling the private interface and public interface. Say libsc4_2.0.3 > was released and I only changed manual pages in 2.0.4. If I decided to > switch from gcc 2.96 to gcc 3.0 in the 2.0.4 release, then I would have > to release libsc5_2.0.4. Thus, to SO_NAME is coupled to both source and > package issues. and earlier: > The problem with C++ is that it is very difficult to make any change > without introducing binary incompatibilities due to possible changes > in inline functions, virtual table layout, and data layout. Even > building the new package with a newer version of the compiler or std > library could cause problems. So, for example, 2.0.1 might be binary > incompatible with 2.0.0, in fact, it probably would be incompatible. The libtool-manual says about c++-libraries: > Creating libraries of C++ code should be a fairly straightforward > process, because its object files differ from C ones in only three > ways: > 1. Because of name mangling, C++ libraries are only usable by the > C++ compiler that created them. This decision was made by the > designers of C++ in order to protect users from conflicting > implementations of features such as constructors, exception > handling, and RTTI. Does this mean I have to put a Depends: g++(= $MY_G++) into libsc-dev's depends? > 2. On some systems, the C++ compiler must take special actions for > the dynamic linker to run dynamic (i.e., run-time) initializers. > This means that we should not call `ld' directly to link such > libraries, and we should use the C++ compiler instead. Is Linux a 'some system'? > 3. C++ compilers will link some Standard C++ library in by default, > but libtool does not know which are these libraries, so it cannot > even run the inter-library dependence analyzer to check how to link > it in. Therefore, running `ld' to link a C++ program or library is > deemed to fail. However, running the C++ compiler directly may lead > to problems related with inter-library dependencies. What does that mean? > The conclusion is that libtool is not ready for general use for C++ > libraries. (Sorry for the longish quotes) So, can anybody point me to documentation on how to handle this, e.g. other c++-libraries who do it 'the right way'? Should I refrain from shipping (shared) libraries? What would happen if I change my c++-compiler but upstream doesn't? Would that mean that SO-names would be out of sync? Is everything easy and changing SO-names is really only needed for interface changes? If so, what does one have to consider? thanks for any hints, Michael
Re: Packaging CVS snapshots?
On Mon, Dec 03, 2001 at 11:15:49PM +0100, Amaya wrote: > Carlos Laviola dijo: > > Some folks at #debian-devel suggested me to use dbs, > > Sorry, what do you exactly mean by dbs? The 'dbs' package :-) > > Can anyone give me some clues, or could anyone that does/has done this > > give me a hand? > > What is exactly what you are having trouble with? > Automating? Dealing with CVS stuff? Yes, I would like to know of an easy way to release frequent (weekly, quarterly, monthly) Debian packages of CVS snapshots of certain software like lopster and licq. > I am also very interested on this subject, but have limited experience. > Just `cvs export` or `cvs-buildpackage` so far :-) That would be cool if one wanted to maintain a CVS repository of his own with his Debian packages, I guess. No? I'm afraid what I want to do here is different... > [Probably should be getting more sleep and not being so inquisitive ;-)] We all need to, apparently :)) -- _ _ _| _ _ | _ . _ | _ to hell with icq, use jabber! (_(_|| |(_)_) |(_|\/|(_)|(_| THIS SPACE INTENTIONALLY LEFT BLANK?
Re: Packaging CVS snapshots?
On Mon, Dec 03, 2001 at 11:56:57PM -0200, Carlos Laviola wrote: > On Mon, Dec 03, 2001 at 11:15:49PM +0100, Amaya wrote: > > Carlos Laviola dijo: > > > Some folks at #debian-devel suggested me to use dbs, > > > > Sorry, what do you exactly mean by dbs? > > The 'dbs' package :-) > > > > Can anyone give me some clues, or could anyone that does/has done this > > > give me a hand? > > > > What is exactly what you are having trouble with? > > Automating? Dealing with CVS stuff? > > Yes, I would like to know of an easy way to release frequent (weekly, > quarterly, monthly) Debian packages of CVS snapshots of certain > software like lopster and licq. > My AM suggested that it is really quite easy to merely apply the debian directory to a cvs export rather that using the ever-so-complicated (and "evil") dbs. Supposedly (I'm maybe wrong here) dbs does not give a clean .orig.tar.gz (which is a bad thing) -- Duncan Findlay