in reply to Config::Ini and IniFile on CPAN?

The CPAN account still has other things there, it is possible the auther simply felt that the many other INI capable modules (also AppConfig) were sufficient. PAUSE is suggesting that authors delete old things (to keep the archive under 650 MB)

--
perl -pew "s/\b;([mnst])/'$1/g"

Replies are listed 'Best First'.
Re: Re: Config::Ini and IniFile on CPAN?
by Flame (Deacon) on May 12, 2002 at 16:06 UTC
    Well, you see, that leads me to a new problem... I was developing a program that was approaching release that used IniFile, however now that it's gone, I can't really ask people to install it can I?


    "Weird things happen, get used to it."

    Flame ~ Lead Programmer: GMS

[reply]
      You might want to peek at Config::IniFiles. I don't have the old module in front of me, but perhaps it may be of some use. Oh woe to the dissappearing dependancies.

          --jb
[reply]
      TIMTOWTDI. As I pointed out, there are other modules.

      --
      perl -pew "s/\b;([mnst])/'$1/g"

[reply]
(RhetTbull) Re: Re: Config::Ini and IniFile on CPAN?
by RhetTbull (Curate) on May 13, 2002 at 02:14 UTC
    Whether or not there are other modules available really isn't the point. I think it's rather bad form to remove a module that people are actively using. I have code that's "in the wild" that uses Config::Ini. Now, that code is effectively broken. The users can't be expected to port it to AppConfig or another config module. I can understand removing old versions and even dropping support but if modules can just disappear, then I will certainly reconsider my use of CPAN.
[reply]
      It is the point in this case, this is software currently under development (or at least that was the impression I got from Flame, perhaps in the CB?). Yes, it's probably not best to remove *every* version of something. On the other hand, CPAN is more like your local public library than the Library of Congress; they can't be expected to keep everything for all time. If your code is "in the wild", isn't it already functional, all dependencies met? Besides it's generally a good idea to keep a virgin copy of the software you use. As Kanji mentioned Backpan (.../AVATAR). Oh, and finally, this would also be a place were code abstraction would be a Good Thing ;-)

      --
      perl -pew "s/\b;([mnst])/'$1/g"

[reply]
        If your code is "in the wild", isn't it already functional, all dependencies met?
        Yes, but the next time someone wants to (re)install it, they can't simply install the required modules per the present README file I distributed. The project in question is distributed to a limited number of people so this point is kinda moot -- it's easy for me to redistribute. It would be a much bigger deal if it were a public project.

        CPAN is more like your local public library than the Library of Congress
        I respectfully disagree with you on that point. If the CPAN? isn't Perl's version of the Library of Congress then I don't know what is! CPAN is the Perl repository!

        Oh, and finally, this would also be a place were code abstraction would be a Good Thing
        Yes, you're right. But should I abstract every module I use? Just in case someone takes it off of CPAN? Perhaps I'll write an abstraction layer for CGI.pm and post to the monastery -- stand clear of the flames! ;-) In this particular case, I did abstact the INI handling stuff so there is no problem in my main program but my abstraction module now needs updating. I only abstracted because I needed some functionality not provided by Config::Ini. That certainly isn't the case with every module I use.

        Besides it's generally a good idea to keep a virgin copy of the software you use.
        Agreed. I'll be sure to be better about that from now on.
[reply]
Re: Re: Config::Ini and IniFile on CPAN?
by samtregar (Abbot) on May 12, 2002 at 20:15 UTC
    PAUSE is suggesting that authors delete old things (to keep the archive under 650 MB)

    I must have missed the memo. Do you have a link to this suggestion?

    -sam

[reply]
      The actual suggestion was "CDROMable", I cannot it locate at this time, IIRC it was on the Delete Files page. You don't have to take my word though, feel free to contact Andreas (I have sent him a message myself actually). (Now that I think about it though, it may be triggered by some threshold which I have fallen below since I did delete some things...)

      --
      perl -pew "s/\b;([mnst])/'$1/g"

[reply]

In Section Seekers of Perl Wisdom