in reply to Posting Packaged Applications

How about just putting your tarball on a web server somewhere and posting a link to it?

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

Replies are listed 'Best First'.
Re^2: Posting Packaged Applications
by ait (Hermit) on Aug 25, 2005 at 17:11 UTC
    That's what I was going to do but I didn't know if it was standard practice here.
[reply]

      I don't think there is a standard practice here for that yet. ;-) Nominally, we point to CPAN for stuff, but if you've not posted it there, yet, there goes "standard practice" ;-)

      Of course, the other question is, why not post it to CPAN? There is the concept of Release Early, Release Often. which may be a useful idea here ;-) GrandFather once wondered about this. Once you put it on CPAN, you can polish it up and release newer and newer versions, and also link to it from here easily.

[reply]

        GrandFather hangs his head in shame and admits that he still hasn't quite got enough rough edges off that particular project to feel he can post it, but will use this as a prompt to get his a into g.

        Perl is Huffman encoded by design.
[reply]
        Thanks for bringing CPAN up in this discussion because I have never been too clear if CPAN is only for libs/modules, or for complete applications.

        For example, this little TkMailer app that I recently posted. I don't plan to maintain it but I think it might help other people. Is this really a candidate for CPAN? If so, I have a few questions:
        • Where can I get a newbie how-to on packaging it for CPAN?
        • How does one know how to clasify it on CPAN?
        • Who defines name spaces in CPAN? Is there a guide for this?
[reply]

In Section Perl Monks Discussion