"I'm guessing we need a couple utilities at the perl infrastructure level: One to "fork" a cpan dist in to github (for dists that aren't on github, but L4P already is), and then an update to cpan/cpanm to get it to prefer where to get a specific dist from."
First, create the repository on your Github. I created one called simply "log4perl", then:
cpan -g Log::Log4perl
tar -xzvf Log-Log4perl-1.49.tar.gz
cd Log-Log4perl-1.49
git init
git add .
git remote add origin https://stevieb9@github.com/stevieb9/log4perl.gi
+t
git push -u origin master
Now you've make a fork of the 1.49 version of the distribution on your own Github.
Now, when you want to install with cpanm:
cd c:\users\steveb\repos
git clone https://github.com/stevieb9/log4perl
cd log4perl
cpanm .
Or, do a make dist in your repository, add the newly created tarball into the repo and do a push, then:
cpanm https://github.com/stevieb9/log4perl/blob/master/Log4Perl-1.53.t
+ar.gz
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|