How do you guys handle library packages in cross-architecture emerges? I found that using portage gave me all sorts of problems when it came to library packages, as the includes, static libraries and dynamic libraries all got installed into the target's rootfs. I also found that the target's include directories & libraries weren't in the search path which caused dependent packages to fail.
-----Original Message----- From: Vladimir Pouzanov [mailto:[EMAIL PROTECTED] Sent: 15 March 2007 11:25 To: [email protected] Subject: Re: [gentoo-embedded] gentoo-embedded buildroot utility On 3/15/07, Natanael Copa <[EMAIL PROTECTED]> wrote: > Then in tbz2's you have everything, including doc's, .a files, headers > etc. If you are not going to use this stuff on your end target, why > waste the bandwith? Sure in our part of the world where we have bandwith > this is no big deal but there are part of the world where bandwith still > is expensive and slow. So I wanted to strip this out from the binary > package. One way to partially achieve this is nodoc/noinfo/noman, however it still keeps headers and other garbage. I'm handling it with a converter to my own tbz2-like format, but I use squashfs to store files. Converter also does the job of splitting tbz to several such squashfs files like abc-2.3, abc-2.3-dev, abc-2.3-man, etc. > Then there was the problem with package that needed to create a user or > something like that in pkg_postinst. Calling pkg_postinst would need to > read the ebuild which would require bash + loads of eclasses. It could > also be be very handy to have a hook for executing something specific my > distro. This was also lacking in tbz2. You have to choose between size and flexibility here. Squashfs pack (I really like this format ;) ) of portage/eclass is 429.90Kb. This is not critical for my handheld, however it would be hard to fit same into my router. -- Sincerely, Vladimir "Farcaller" Pouzanov http://hackndev.com -- [email protected] mailing list -- [email protected] mailing list
