* Take MAINTAINERship, ok by schmonz@.
* Libtoolized.
* Fix typo in variable name.
* Set LICENSE as public-domain.
Changelog:
tinycdb-0.78 2012-05-11
- bugfix release:
o fixed >2Gb file size prob on 32bit platform
o fixed handling of files >=4Gb
o fixed a few compiler warnings
- introduce $(LD) and $(LDFLAGS), and also $(CDEFS) in Makefile
All:
- include/schily/stat.h now contains macros to set the nanoseconds
in timestamps in a OS independent way
Mkisofs (Maintained/enhanced by Jörg Schilling since 1997, originated by Eric Youngdale):
- mkisofs now identifies itdelf by default (inside the APPID string)
as being UDF capable.
- mkisofs now sets link count and "unique id" == inode number for files.
Note that this may still not result in useful hardlinked files on all
platforms as e.g. Solaris and Linux ignore the UDF unique ID and rather
use the location of the file_entry as inode number. This will never
return the same number for different filenames that point to the
same file data and thus prevents hard linked files from being visible.
This is however not a Solaris problem, the problem is rather in the
UDF standard that does not require the unique id to be in a 32 bit
range as long as the media size is = 8 TB. Note that 32 bit UNIX
programs cannot access files with an inode number that cannot be
expressed as 32 bit number, so inode numbers that do not fit into
32 bits may cause problems. Ths only way to work around this problem
would be to enance the Solaris and Linux UDF filesystem module to
recognize whether a filesystem has been created by mkisofs that grants
useful inode numbers. The same is already done for ISO-9660.
- mkisofs now supports additional file types with UDF:
- named pipes
- sockets
- character devices
- block devices
- mkisofs now supports all three UNIX times with microsecond granularity in UDF
- mkisofs now sets correct user/group/permission for symlinks in UDF
- mkisofs now supports S_ISUID, S_ISGID, S_ISVTX (set uid, set gid, sticky) in UDF
in modules (the files in ${WRKSRC}/library), as they're treated as
data and not scripts - the right thing to do is to set
"ansible_python_interpreter" in the configuration.
Also, install example files in ${PREFIX}/share/examples/ansible.
- install manpages
- replace "etc" with PKG_SYSCONFDIR in a number of locations
- replace "usr/share" with @PREFIX@/share in some places
- do some cleanup so things install with PKG_DEVELOPER set.
