Almost exactly 3 years ago there was much discussion about versioning perl modules. Having read several of those threads, I don't feel so bad about not understanding.
I have a couple issues: When I picked up several modules from that most prolific maintainer, None, the modules were already versioned, so my world view became "most pms are versioned". When one of my modules needed an additional module that hadn't been in fink before, I just went and made it versioned (even though I picked the pure perl version -- text-csv-pp-pm -- because I didn't want to mess with C code in perl). Do I knuckle down and figure out if it really needs to be versioned, and fix it if it doesn't? Or can I be slovenly and say, "I dug this hole, it's not too deep, I can live with it this way"? Second issue: Now that Leopard is out there stalking in the weeds, it seemed like a good idea to create 588 versions of my modules. That went smoother than I expected, and they're even all running in support of my copy of gnucash2. So now, do I modify the gnucash2.info file to say: Depends: mmm-pm586 | mmm-pm-588, nnn-pm586 | nnn-pm588 for all the modules? Or is there a shorter way? Other considerations that I'm not-so-blissfully unaware of? Dave -- David Reiser [EMAIL PROTECTED] ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
