On Wed, Jan 27, 2010 at 07:01:17PM +0100, Marc Kleine-Budde wrote:
yeah, you can delete some rules, but I don't don't which. But Michael
knows.
For now it's just prepare that can be deleted. And that's only a side
effect. I'm working on a patch for that. Something like:
PKG_SOURCE not defined -
Hi,
for all packets, which do install properly into PKGDIR using the
default install rule, it would be desireable to have an 'install_auto'
macro which,
- scans the the PKGDIR and creates appropriate control data for ipkg
to replicate this content.
- by default filters paths like /usr/share/man
Hi,
I got some problem with a packet that stores it libraries in
/usr/lib/pkgname/libfoo*. This requires rpath-link options for the
linker and autoconf correctly creates the right options.
The patchin macro fixes up the configure and libtool config to not use
rpath-links. This helps with
Carsten Schlote wrote:
I got some problem with a packet that stores it libraries in
/usr/lib/pkgname/libfoo*. This requires rpath-link options for the
Just for curiositywhy does it store its libs in there?
linker and autoconf correctly creates the right options.
Note: rpath !=
Carsten Schlote wrote:
Hi,
for all packets, which do install properly into PKGDIR using the
default install rule, it would be desireable to have an 'install_auto'
macro which,
- scans the the PKGDIR and creates appropriate control data for ipkg
to replicate this content.
- by default
Hi
For the 'ptxdist images' run, ipkg files from PKGDIR are used, which do
not have a -1 suffix attached.
The ipkg-repository created by ipkg-push creates a dist of the same
files and attaches a -1..n suffix to the version part of the ipkg
filename for each file.
When booting from a flash image
