From: Andriy P. <fre...@ua...> - 2003-09-05 15:06:44
|
Hello Earnie, Friday, September 5, 2003, 3:45:14 PM, you wrote: EB> Andriy Podanenko wrote: >> Hello mingw-dvlpr, >> >> ported to mingw and tested >> >> http://opera7up.narod.ru/download/mingw-ddk/log4cpp-0.3.4b.tar.bz2 EB> Assuming that you built this for host mingw32, you will need to use EB> --prefix=/mingw and so - how to bzip2 that package? I make so (this is for binary only) configure --prefix=/usr/install/$PKGNAME make make install cd /usr/install/$PKGNAME && tar -cf * && bzip2 -z *.tar this is not wrong, because if U decompress package U will have the same as on the sf.net/projects/mingw EB> in the configuration. Also when the package is archived EB> one directory tree level too high. I.E.: The unarchive needs to install EB> to bin/, lib/, etc. You are also missing a doc/log4cpp/ directory that EB> should contain the licensing file from the source package (E.G.: EB> COPYING.LIB) AUTHORS of original package didn't copy that file when do make install, so why I need do that(in binary distribution)? But if it is important - I`ll do it of course EB> , any pertenate README type of file, a PORTNOTES file that EB> contains highlevel notes on what you needed to do to build the package. Ok, I understand, if i want to make port I must to make patch for the source only! EB> and a PORTPATCH file of the ``diff -u3p original modified'' output. If EB> you have no modifications then the PORTPATCH file should state that. A EB> ``cvs diff'' can also be used if you have a local cvs directory setup. EB> Also, take a look at http://www.mingw.org/download.shtml#hdr4 for tips EB> on MinGW package naming conventions. why naming conversion for official release of original package? sorry for my words, but I came to mingw from FreeBSD and use BSD ports tree for developing and porting(may be I can help to build such tree for msys( http://www.freebsd.org/ports/ ) ? What U say?), so my mind is distored by FreeBSD`s policy. EB> Earnie. |