http://qs1969.pair.com?node_id=685814


in reply to Re: The App:: namespace? Sharing a webapp on CPAN
in thread The App:: namespace? Sharing a webapp on CPAN

as I noted in my OP, a major major headache is how to deal with CPAN modules the app needs. If the webapp was on CPAN, I could just make a makefile or Build script that says, "Hey, these are required, so go and get 'em".

That's maybe 80% of my wanting on CPAN. As for the rest of the installation of the program, it could be as easy as a small perl script that moves the appropriate files, to the appropriate places (say into the public_html of the account you're installing into) and then a little message that says, "To finish the installation, visit $some_url in your web browser" and we're done .

The other large issue is the testing suite for the webapp is almost never used outside of myself.

There's some other interesting issues that I think CPAN will help out, many to do with diversification of Perl, etc, etc.

-justin simoni
skazat me

Replies are listed 'Best First'.
Re^3: The App:: namespace? Sharing a webapp on CPAN
by dragonchild (Archbishop) on May 10, 2008 at 02:46 UTC
    If the webapp wasn't on CPAN, you could do the same thing. Or, you could just bundle the modules you need and, that way, you're guaranteeing the proper versions. Just because you require v1.34+ doesn't mean that 1.35 didn't break something you need.

    As for everything else you're talking about, these things don't require CPAN. They are installation process issues. Don't worry about "diversification of Perl" issues. Forcing everyone to come to CPAN just to get your app means you're limiting your userbase to Perl users. I shouldn't be forced to care about what language you've implemented in. I only know what language Trac is implemented in because I had to patch it once. I don't know what language Jira, gVim, Firefox, or iTerm are written in ... and I don't care.


    My criteria for good software:
    1. Does it work?
    2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

      If the webapp wasn't on CPAN, you could do the same thing. Or, you could just bundle the modules you need and, that way, you're guaranteeing the proper versions. Just because you require v1.34+ doesn't mean that 1.35 didn't break something you need.
      This already happens with the webapp, as it has ver 1 of the CPAN module bundled. Sometimes, 1.1 ver of the CPAN module gets installed site wide and things blow up. I'm hoping this won't happen - or if it does, I'll know about it, at the same time as everyone else.

      Forcing everyone to come to CPAN just to get your app means you're limiting your userbase to Perl users.

      I'm not forcing anyone, it just another alternative, *specifically* for perl geeks, with a lot of benefits. Non-Perl geeks don't know how to use CPAN and that's the current userbase. I'd like to grow the userbase.

      If you don't care, why are you expressing an opinion?

      -justin simoni
      skazat me

        I don't care what language the apps I use are written in. I do care about how applications are distributed and installed. Distribution from CPAN is a very non-ideal way. There are much better ways to distribute and install. Hence, why I'm expressing an opinion.

        My criteria for good software:
        1. Does it work?
        2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?