On Fri, 9 Apr 2010, Alexander Churanov wrote:
2010/4/9 Leinier Cruz Salfran <salfrancl.lis...@gmail.com>
i want to ask you one thing: can you make the 'pkg_install' suite reusable
.. means install 'libinstall.a' as a shared object in order to make it
reusable by others devs
I'd like to add my 50 cents. From my point of view, the true UNIX way is
re-using whole programs. This provides unbelievable isolation and
correctness. If you don't want to fork myriads of processes each second,
then, it's, probably, better to ask for pipe mode of pkg_* tools. For
example, aspell works that way. You start a process, write commands and
queries and read results.
While there are clearly benefits to process isolation, there are countless
situations in UNIX where I've said to myself "Oh, I wish I had a lib<foo> not
just a <foo> command". This is particularly the case for monitoring tools,
where third-party applications have a lot of trouble parsing and tracking the
output of tools like ps(1), etc. This is why recently we've been working on
libmemstat(3), libprocstat(3), libnetstat(3), etc -- so that tools can avoid
rewriting that code as well as avoid the parsing problem. So I have no
particular opinion on this tool, but I will say that in general, it would be
nice if programs were often thin wrappers around a library that could be
reused, not just command line tools.
Robert
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
