-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 03 October 2003 17:49, Daniel Reed wrote: > On 2003-09-30T13:13+0200, Stefan Hetzl wrote: > ) Please upload the mhash and mhash-devel packages: > ) > ) mhash: > ) http://stud3.tuwien.ac.at/~e9925353/cygwin/release/mhash/setup.hint > ) > http://stud3.tuwien.ac.at/~e9925353/cygwin/release/mhash/mhash-0.8.18-1-src >.tar.bz2 ) > http://stud3.tuwien.ac.at/~e9925353/cygwin/release/mhash/mhash-0.8.18-1.tar >.bz2 ) > ) mhash-devel: > ) > http://stud3.tuwien.ac.at/~e9925353/cygwin/release/mhash/mhash-devel/setup. >hint ) > http://stud3.tuwien.ac.at/~e9925353/cygwin/release/mhash/mhash-devel/mhash- >devel-0.8.18-1.tar.bz2 > > One minor nit in the final review: Both mhash and mhash-devel include the > file usr/share/doc/Cygwin/mhash-0.8.18-1.README. I believe sub-packages are > supposed to include their own unique .README (or at least not overwrite > files included in the parent package). For example, ncurses includes > usr/share/doc/Cygwin/ncurses-5.3.README while libncurses-devel includes > usr/share/doc/Cygwin/libncurses-devel-5.3.README. I used the same approach for the libmcrypt packages. Both libmcrypt-2.5.7-1 and libmcrypt-devel-2.5.7-1 contain the file: usr/share/doc/Cygwin/libmcrypt-2.5.7.README
> I am only concerned if this might cause problems for setup during uninstall > or any other operations. If not, I believe the package can be uploaded > as-is. I don't know if this will cause a problem, I just hoped it wouldn't. Should I change it (both in libmcrypt and mhash) ? Greetings, Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE/faGRKN/5Ocgn19gRAixuAKCO+b4RvhfyqvoeQ6VFbfQz/X8dhgCff7Nb n/bks7CHJVuqIpa9Z66Cha0= =CGdD -----END PGP SIGNATURE-----
