Are PPM/RPM repositories likely to happen or be a good idea?

IMHO, the CPAN repository should be as platform-agnostic as possible. Of course, things in the Win32:: namespace will rarely, if ever, be useful outside Windows. Even so, things on CPAN need to install the same way on a broad range of platforms.

There is an argument that fledgling package systems could make use of the CPAN mirrors instead of going to the trouble of setting up its own mirror system. For those people, I suggest looking at an article I wrote for the Linux Journal a while back on Using Debian Apt-get over Freenet. It makes use of Freenet's FProxy (a gateway that lets you use Freenet over HTTP) to allow any package management system that can support HTTP to use Freenet. The article is specific to Debian, but the approach could probably be generalized to almost any package manager with HTTP support.

(Note that I've stepped away from the Freenet project, so things might have changed since I wrote the article. However, I imagine FProxy is still there and the basic approach will still work.)

----
send money to your kernel via the boot loader.. This and more wisdom available from Markov Hardburn.


In reply to Re: Module::Build and the PPM by hardburn
in thread Module::Build and the PPM by barbie

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.