Re: [RFC] [Cross Toolchain] Multiarch and sysrooted toolchain

Neil Williams writes: > On Wed, 11 Mar 2009 14:50:19 +0100 > Goswin von Brederlow wrote: > >> > >> > [*] >> > I have been looking lately into making some cross toolchain >> > improvements, one of them will be to change to a sysrooted cross >> > toolchain, but the current layout we are using b

Re: Transition from dpkg to GNU install-info

I went ahead and rewrote a bit the plan and removed stuff that did not seem to apply to this transition and placed it in a wiki page, . Hope you don't mind. On Wed, 2009-03-11 at 08:49:07 +0100, Norbert Preining wrote: > On Mi, 11 Mär 2009,

Re: Transition from dpkg to GNU install-info

On Wed, 2009-03-11 at 09:40:46 +0100, Norbert Preining wrote: > Ok, here is a package, crude, nothing tested, but it is there: > deb http://people.debian.org/~preining/TeX/ i-i/ > deb-src http://people.debian.org/~preining/TeX/ i-i/ Sorry, I've not yet had the time to take look, maybe

Re: Transition from dpkg to GNU install-info

On Do, 12 Mär 2009, Guillem Jover wrote: > . Hope you > don't mind. Great, thanks. > I think it'd be better to not entangle those two changes, so I'd put it > in the same place as the current install-info from dpkg. A transition > from /usr

Re: Transition from dpkg to GNU install-info

On Wed, 2009-03-11 at 12:13:47 +, Neil Williams wrote: > What I really need, in order to test properly, is a package that can > trigger install-info. I admit, I'm a bit unfamiliar with triggers still > - what do I need to change in a package (say coreutils) that currently > contains an info doc

Re: Transition from dpkg to GNU install-info

On Do, 12 Mär 2009, Guillem Jover wrote: > > deb http://people.debian.org/~preining/TeX/ i-i/ > > deb-src http://people.debian.org/~preining/TeX/ i-i/ > > Sorry, I've not yet had the time to take look, maybe this weekend. Anyway, I am testing a package that includes already trigger suppor

Re: Transition from dpkg to GNU install-info

Hi all, Ok, I have new packages available which do: - support triggers, if a file is dropped into /usr/share/info then the trigger action of install-info postinst is called. That is nothing else but calling update-info-dir - the wrapper install-info is now trivial: ginstall-i

Re: [RFC] [Cross Toolchain] Multiarch and sysrooted toolchain

On Thu, 12 Mar 2009 10:31:03 +0100 Goswin von Brederlow wrote: > > I thought mulitarch wanted: (this is making a lot more sense now.) So, updating: > > /usr/ > > |-- include/ > > | `-- $arch-linux-gnu/ > > | `-- foo.h > >`-- lib/ > > `-- $arch-linux-gnu/ > >

Re: Transition from dpkg to GNU install-info

On Thu, 2009-03-12 at 14:34:41 +0100, Norbert Preining wrote: > On Do, 12 Mär 2009, Guillem Jover wrote: > > > - can you prepare a dpkg experimental package that does not ship ii but > > > depends on install-info? > > > > As per the transition plan dpkg will still ship a dummy script that > > wa

Re: Transition from dpkg to GNU install-info

On Thu, 12 Mar 2009 16:00:26 +0200 Guillem Jover wrote: > On Wed, 2009-03-11 at 12:13:47 +, Neil Williams wrote: > > What I really need, in order to test properly, is a package that can > > trigger install-info. I admit, I'm a bit unfamiliar with triggers still > > - what do I need to change

Re: Transition from dpkg to GNU install-info

On Do, 12 Mär 2009, Guillem Jover wrote: > install-info do nothing if called from inside a maintainer script by > checking for the DPKG_RUNNING_VERSION environment variable for example > (this can go once the wraper in install-info disappears). What about that code in install-info (I am not sure i

Re: [RFC] [Cross Toolchain] Multiarch and sysrooted toolchain

>> The question is >> >> /arm-linux-gnu/lib/libfoo.so > l> /usr/arm-linux-gnu/[usr/]lib/libbla.so >> /usr/arm-linux-gnu/[usr/]include/foo.h >> >> or >> >> /lib/arm-linux-gnu/libfoo.so >> /usr/lib/arm-linux-gnu/libbla.so >> /usr/include/arm-linux-gnu/foo.h >> >> It has always been a question of wher

Re: Transition from dpkg to GNU install-info

On Thu, 12 Mar 2009, Norbert Preining wrote: > - install-info is installed in /usr/sbin and the package carries a > Replaces: dpkg (<= 1.14.25) which is current unstable version The Replaces has to be unversioned if dpkg continue to ship a no-op /usr/sbin/install-info (which is the plan seen on

Re: Transition from dpkg to GNU install-info

On Do, 12 Mär 2009, Raphael Hertzog wrote: > I would rather have the new install-info in /usr/bin/, and dpkg > ships an /usr/sbin/install-info that does nothing but calls > /usr/bin/install-info if it exists and warn otherwise. (And also warn if > it's called with the full path). That sounds fine

Re: [RFC] [Cross Toolchain] Multiarch and sysrooted toolchain

Hello, I have been talking with Guillem on IRC, he has point me to a reference[1], that might be useful. [1] http://lackof.org/taggart/hacking/multiarch/ Regards -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lis

Re: [RFC] [Cross Toolchain] Multiarch and sysrooted toolchain

Neil Williams writes: > On Thu, 12 Mar 2009 10:31:03 +0100 > Goswin von Brederlow wrote: > >> > I thought mulitarch wanted: > > (this is making a lot more sense now.) > > So, updating: > >> > /usr/ >> > |-- include/ >> > | `-- $arch-linux-gnu/ >> > | `-- foo.h >> >`-- l

Re: [RFC] [Cross Toolchain] Multiarch and sysrooted toolchain

Hello Simon, > install anything but libraries and headers into /usr/ -- so I > don't think there is a pressing need to replicate a filesystem hierarchy > standard below a triplet directory. That is what GNU people expect when building cross tools, they use a switch called sysroot for it and it is

Re: [RFC] [Cross Toolchain] Multiarch and sysrooted toolchain

Hector Oron writes: > Another issues i am thinking about are the emul/ia32-linux i believe > that is scheduled to disapear soon and we are also forgetting mips > tri-arch. This is still hardcoded in the ia64 kernel. So at least a link for it must remain at least on ia64. Apart from that we the

Re: [RFC] [Cross Toolchain] Multiarch and sysrooted toolchain

Hector Oron writes: > Hello, > > I have been talking with Guillem on IRC, he has point me to a > reference[1], that might be useful. > > [1] http://lackof.org/taggart/hacking/multiarch/ > > Regards That is a nice non Debian specific writeup (i.e. it doesn't go into any of the implementation de

Re: [RFC] [Cross Toolchain] Multiarch and sysrooted toolchain

Hi, On Wed, Mar 11, 2009 at 12:40:39PM +0100, Hector Oron wrote: > /{include,bin,lib,lib64} > Mainstream code expects a different layout more LHS compliant, > /{usr/include,bin,lib,lib64} "usr/include" looks horribly wrong to me, since it cannot be achieved in a cross build by changing the -

Re: [RFC] [Cross Toolchain] Multiarch and sysrooted toolchain

On Thu, 12 Mar 2009 19:39:11 +0100 Simon Richter wrote: > I think treating cross-building as largely orthogonal to supporting > multiple runtime ABIs on the same system isn't the worst of ideas Maybe not, but it isn't a sustainable idea. >, since > they have entirely different objectives Not e

Re: Transition from dpkg to GNU install-info

On Thu, 12 Mar 2009, Norbert Preining wrote: > But should we ship the wrapper or GNU install-info itself as > /usr/bin/install-info? > > If we can assure that the /usr/sbin/install-info is called from the > maintainer scripts (there /usr/sbin should be in front of /usr/bin) > I could simply drop t

Re: Transition from dpkg to GNU install-info

On Do, 12 Mär 2009, Raphael Hertzog wrote: > Relying on the order inside PATH is too fragile IMO. If you want to have > the binary as install-info directly, you'll have to wait until > install-info is not used any more by debian packages, i.e. for squeeze+1. Ok, let me sum up the approach as I und