On Fri, Dec 10, 2010 at 04:23:32PM +0100, Pierre Habouzit <[email protected]> wrote: > Huh ? if you want rxvt-unicode when ssh-ing to systems that haven't it > installed, yes it's better to make the terminfo entry be included in > ncurses which is pervasive (unlike urxvt). It has nothing to do with > Debian...
Except that this only works on debian, as debian doesn't have the power (and doesn't even try) to include the temrinfo in ncurses. All it does is patch *their* variant of ncurses. So of course this only has something to do with debian, as it only affects the debian ncurses package. > ...or its policy. You might want to read http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=270243 Yes, rxvt-unicode was delivered with the wrong TERM=rxvt setting in sarge because it wasn't allowed to install it's own terminfo file. Since it would have been possible for both ncurses-base and rxvt-unicode to handle this in an upgrade-safe way (dpkg is not _that_ limited), it wasn't done. If something isn't a technical limitation but a political one, you call this policy - there was no other reason for this breakage. And TERM=rxvt is far more compatible than TERM=rxvt-256color (despite the name, the latter doesn't debian policy and generally defines the wrong keycodes - if you are confused, ask somebody who knows...). > > > Marc: you may consider to upgrade your makefiles so that the make > > > install is > > > > Sorry, Pierre, but take your idiotic insults somewhere else. > > I fail to see where I insulted you, unless saying that your > build-system "install" target is buggy is an insult. It is, because you well know it's a lie. > But I love you too. I don't love you, sorry. I think you are just an arrogant asshole. But nice try to avoid the technical questions and the facts by making it personally. > > We don't use any automake-fu anywhere, and the far majority of > > software doesn't support this, which is entirely a debian requirement. > > When you use autotools, you have to respect DESTDIR (not prefix= > indeed). We use autotools, and no, we don't have to respect DESTDIR. > It has absolutely nothing to do with Debian, and since you > don't seem to believe me (and I'm sure you'll say that I'm an idiot > despite the pointers, but I couldn't care less), for the other > interested people, here are the pointers: > - http://sourceware.org/automake/automake.html#DESTDIR > - http://sourceware.org/automake/automake.html#Hard_002dCoded-Install-Paths Maybe you should read it yourself, nothing there says it is a bug not to, or even that you need to do that. I herewith call your bluff: you made a statement, tried to make people believe it by running around with important-looking URLs, but when one actually checks them, one can see you are just a liar. If you are not a liar, why do you make these claims when the pages you refer to obviously disagree with you? > which is *exactly* what you're doing: installing to a hard-coded (in > tic) path. Another lie: there is nothing hardcoded in rxvt-unicode, nor in tic (RTFM, the manpage explains it on debian, I just checked) Outside debian, the behaviour of tic is the corretc one by definition. Your patch breaks urxvt for *everybody else*. We, as upstream, create a distribution for people to download and install. If debian has special requireemnts that collide with that, they cna either nicely ask for us to support this in addition to the correct solution, or patch it (if they know what they are doing, and I assume that package maintaieners at least have some basic understanding of how their distribution packaging system works). What you are aksing for is to break our standalone distributon and create something that works fine when building a debian package only. As best, that's naive, but in your case, since you are well aware of that and call it a "bug", it's just arrogance. I am sorry, supporting people compiling their rxvt-unicode themselves is NOT a bug for anybody who is even remotely reasonable. > It seems that you have no clue how packaging software works (which is > all fine, that's not something you're supposed to do as an upstream). Maybe, but you can be sure that I would have done a better package than the current maintainer or you. At least I have shown better understanding of DESTDIR (you didn't even know the env variable name), terminfo issues in general and how debian specifically handles them, compatibility with past debian versions and other systems etc. etc. > Maybe you should listen to people trying to improve your build system Well, where are those people? All we have is a maintainer who gives a shit about improving the build system and you, a liar who doesn't even know how their distribution handles terminfo files and just wants us to break our package for everybody in the process. Really, take a breath and think about this. I am sure if you honestly try to understand the issue, and this and my previous mails, you will realise how wrong you are, and maybe in the future behave more sensible, and maybe you even learn something about debian in the process. This is the only reason I care to reply. -- The choice of a Deliantra, the free code+content MORPG -----==- _GNU_ http://www.deliantra.net ----==-- _ generation ---==---(_)__ __ ____ __ Marc Lehmann --==---/ / _ \/ // /\ \/ / [email protected] -=====/_/_//_/\_,_/ /_/\_\ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
