Shantanu Bhadoria

Bangalore.pm meetup 6th August 2011

2011-08-07T22:23:00Z

Last month we kicked of the meetups for the fledgling Bangalore.pm group. Our first meetup in July was attended by 3 devs including myself to kick things off, this saturday we had our second ever meetup of Bangalore.pm.
The meetup was attended by Venkat(wolf), kumar ravish and yours truly from the first time and one new member in form of Krishna Abbina from my team at work. We met up at Legends of Rock at Koramangala,(the place serves delicious cheese bites)
We mostly talked about Perl and its application to our daily chores. Each of us come from a diverse background w.r.t. what we do with perl and it made for some very fruitful discussions and KT! :)

Ofcourse the Bangalore.pm mailing list has a lot more members than the number that have attended our meetups till now, the number of Perl developers in Bangalore being even bigger! So to sum it up we have really high hopes for this group and we are hoping to add new members to every meetup in the time to come.

If you are a perl dev in bangy and looking to network/interact with other fish in the perl pond you should look us up for the next meetup dates and venue at bangalore.pm.org.

Bangalore.pm meets next at 7:30 PM on 7th September,2011 in Legends of Rock, Koramangla.

**WE NEED YOU**

Acme::CPANAuthors::India

2011-07-21T12:14:37Z

I just released the Acme::CPANAuthors::India today, Its based on the Acme::CPANAuthors. There are similar pre-existing modules for other countries and especially extensive ones for most of europe in the Acme::CPANAuthors::* namespace but surprising India was missing in the list despite the large group or perlers here.

This also gave me the chance to use Dist::Zilla or dzil for the first time to do my module packaging. I like all the additional features that the plugins add to your distribution. especially the auto versioning, auto Generation of Module's README, MakeFile, Pod tests, METAs from your pod documentation is very cool. I do miss the more filling module template that ModuleMaker generates for the module itself however. I am sure there must be a way to generate a more comprehensive module template here. I am still looking and will update this thread with more soon.

Acme::CPANAuthors::India seeks to get all the CPAN Authors in India together into a single list for reference and link ups.
If you are supposed to be on this list and aren't then you can raise a bug at RT for this module at http://rt.cpan.org/NoAuth/Bugs.html?Dist=Acme-CPANAuthors-India with your Full Name and CPAN ID/HANDLE.

]]> I just released the Acme::CPANAuthors::India today, Its based on the Acme::CPANAuthors. There are similar pre-existing modules for other countries and especially extensive ones for most of europe in the Acme::CPANAuthors::* namespace but surprising India was missing in the list despite the large group or perlers here.

This also gave me the chance to use Dist::Zilla or dzil for the first time to do my module packaging. I like all the additional features that the plugins add to your distribution. especially the auto versioning, auto Generation of Module's README, MakeFile, Pod tests, METAs from your pod documentation is very cool. I do miss the more filling module template that ModuleMaker generates for the module itself however. I am sure there must be a way to generate a more comprehensive module template here. I am still looking and will update this thread with more soon.

Acme::CPANAuthors::India seeks to get all the CPAN Authors in India together into a single list for reference and link ups.
If you are supposed to be on this list and aren't then you can raise a bug at RT for this module at http://rt.cpan.org/NoAuth/Bugs.html?Dist=Acme-CPANAuthors-India with your Full Name and CPAN ID/HANDLE.

File::UStore a UUID based File Storage Abstractor, Why would a temp folder not be writable???

2011-07-18T13:59:41Z

Its been a few months since I released the File::UStore module to cpan and it has gradually attained stability over time. Not that there were a lot of bugs to begin with. Most of the bugs were in the tests rather than the code. Given the inherent complexity of writing a test for File Manipulation module for multiple platforms, I almost expected this. CPAN Testers are particularly thorough w.r.t the number of platforms their automated installer tests for a module. and it gives a nice chart of how your module fared in all those placesKudos to them for that! here is a link for th results of File::UStore http://www.cpantesters.org/author/S/SHANTANU.html#File-UStore.
In fact there are still some tests that File::UStore fails at CPAN Testers, Primary reason being that some 2-3 of the platforms(some Solaris and fedora distros) that the module is tested on did not have their temp folders writable. I am using one of the CPAN Modules for getting a temp folder for the tests and as it turns out that folder is un-writable for some platforms. Now I am not sure why a platform would do that. If it is a temp folder it should be generally writable isn't it?
Anyway the module itself works and I am fairly confident with it. If the tests fail on your platform you can simply use the force option to install it and try it out.

About the Module :
This module was born out of a need for a File storage abstracter that doesn't automatically dedup files like the usual hash based Storage modules do. Due to the nature of File Hashing, Hashed Storage doesn't allow duplicates. If the same file is stored a second time using Hashed Storage it transparently returns the same hash it had returned last time as an id without adding any new file in storage due to inherent character of hash based storage, while this is useful if a user doesn't want any duplicates occurring in a storage, this apparently trivial difference is risky in the use case where two processes upload a duplicate file to the store and both processes want to do file handling simultaneously, only one of the processes will be able to get a lock(deletion,manipulation etc.) on the file at a time and if the first process deletes the file referred to by its ID, the second process will never know what happened to the file it added.