With increasing number of servers and administrators it becomes more and more difficult to keep track of what is where doing what and why. Somebody added a configuration file and three weeks later somebody else wonders what it is for or whether it was temporary or not and why something was changed in the first place. By this time even the author of that change may not remember exactly it was for. Like a firewall rule or Apache's virtual host. Or perhaps an unfortunate update overwrote some configuration file somewhere, maybe with administrator's help even. Who and how will notice that? Remembering such things and anxiety of lack of assurance puts a really huge overhead while administrators could focus on real work. Revision control systems help somewhat in this, committing configuration file with relevant commit logs goes a long way as far as documenting changes is concerned, but will everyone always remember to commit changes? Here comes the aforementioned overhead of remembering things. Now what really lets administrators focus on work instead of worrying about everything? Reliable monitoring systems calmly reminding them "everything is fine" when it is. Applying the same approach to managing configuration versions, notifying administrators when something changes or isn't committed, resulted in creation of "PMSVN". That was only the beginning though, PMSVN can do more than that since more matters were required to be easier. Control over what is in revision control system and what isn't cam be annoying in Subversion. Like controlling /etc/hosts and /etc/fstab, but not /etc/shadow or whole /etc is just too much bloated. PMSVN eases that by letting you choose, which files to control and monitor. Synchronize and monitor consistence of small bits of configuration, which on most or every server was the same, e.g. NTP or SSMTP. It would be nice to be keep such configuration in one place and being able to let it propagate across servers easily. That's also one of PMSVN's features.
Created attachment 233245 [details] pmsvn-1.0.ebuild
Created attachment 233281 [details] pmsvn-1.0.1.ebuild version bump corrected path in einfo message in pkg_postinst()
Created attachment 233309 [details] pmsvn-1.0.2.ebuild version bump - ebuild identical as 1.0.1
Your ebuild looks goo, there are some minor points like missing `|| die` to the o* functiions and EAPI=3 compliance (EAPI=2 is met). I would be happy to see you in ... Hello, The Gentoo Team would like to firstly thank you for your ebuild submission. We also apologize for not being able to accommodate you in a timely manner. There are simply too many new packages. Allow me to use this opportunity to introduce you to Gentoo Sunrise. The sunrise overlay[1] is a overlay for Gentoo which we allow trusted users to commit to and all users can have ebuilds reviewed by Gentoo devs for entry into the overlay. So, the sunrise team is suggesting that you look into this and submit your ebuild to the overlay where even *you* can commit to. =) Thanks, On behalf of the Gentoo Sunrise Team, Michael "not a sunrise member yet" Weber. [1]: http://www.gentoo.org/proj/en/sunrise/ [2]: http://overlays.gentoo.org/proj/sunrise/wiki/SunriseFaq
I will take it
On tree Thanks for reporting and for the ebuild :)
