[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Packaging _still_ wasteful for many large packages



In article <1076980265.40316a29274ed@www.linuxops.net> you write:
>
> 6233996  17700       17680 99 pool/main/r/rhyme/rhyme_0.9-3_alpha.deb
> 6379374  15760       15748 99 pool/main/r/rhyme/rhyme_0.9-3_arm.deb
> 6442732  15764       15748 99 pool/main/r/rhyme/rhyme_0.9-3_hppa.deb
> 6290182  15688       15676 99 pool/main/r/rhyme/rhyme_0.9-3_hurd-i386.deb
> 6379376  15760       15748 99 pool/main/r/rhyme/rhyme_0.9-3_i386.deb
> 6170132  17856       17828 99 pool/main/r/rhyme/rhyme_0.9-3_ia64.deb
> 6441090  15760       15748 99 pool/main/r/rhyme/rhyme_0.9-3_m68k.deb
> 6442940  15772       15748 99 pool/main/r/rhyme/rhyme_0.9-3_mips.deb
> 6381082  15772       15748 99 pool/main/r/rhyme/rhyme_0.9-3_mipsel.deb
> 6443174  15768       15748 99 pool/main/r/rhyme/rhyme_0.9-3_powerpc.deb
>
>I maintain rhyme.  The GDBM files rhyme uses (apparently) aren't actualy cross
>platform, so probably should NOT go in /usr/share.  I have to admit to not
>having tested this.  (yes, remiss of me)
>
>When I have time (will be two or three weeks at least) I'll build it for all
>available architectures I have accounts for as a split package and see how it
>does.  If it turns out that they are truly not platform independent then I'll
>have to find somewhere else to put them.  Does anyone have any suggestions?
>/usr/lib/rhyme perhaps?

If they are specific, then yes /usr/lib/rhyme would be best.

>If they aren't architecture specific then I will split them into a seperate
>arch-all package.

Sounds good to me.

>
>In this case, you are quite correct, it IS a bug.  My apologies for not having
>noticed it earlier.
>
>Please do file a report about it.

Expect one shortly.

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
Can't keep my eyes from the circling sky,
Tongue-tied & twisted, Just an earth-bound misfit, I...



Reply to: