<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Correct - and he has every right to make his own decisions.<br>
<br>
That said, if I take a leaf from Linux kernel development or the Gentoo
package tree, I can easily overlay a snapshot branch of any package I
like, simply by setting an environmental variable. The point being
that I can happily release my own version of H::T without breaking
anyone else's version. And I can do this without forking the namespace.<br>
<br>
Having looked at CPAN module install semantics, I was under the
impression that it was possible for two independent people to upload
their modules. Then using the cpan shell, a user could fetch a
specific developer's version of a package, as in:<br>
<br>
cpan> install M/MA/Mathew/HTML-Template-2.8_01.tar.gz<br>
<br>
thoughts?<br>
<br>
Mathew<br>
</tt><br>
<a class="moz-txt-link-abbreviated" href="mailto:leif.eriksen@hpa.com.au">leif.eriksen@hpa.com.au</a> wrote:
<blockquote cite="midA50A7BED086A434798E06E70BB72F8918745DD@exchange2k"
type="cite">
<pre wrap="">The decision to create a new namespace has already been made for you by
the H::T developer - he doesn't want your extra features in his
namespace, so you need another.
Did he give a reason - I suspect he felt the new features didn't fit
with his idea of what H::T should do. The doco and design seem to
indicate they have refined H::T to be exactly what they want.
L
-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:mathew.robertson@netratings.com.au">mathew.robertson@netratings.com.au</a>
[<a class="moz-txt-link-freetext" href="mailto:mathew.robertson@netratings.com.au">mailto:mathew.robertson@netratings.com.au</a>]
Sent: Thursday, 9 March 2006 12:32 PM
To: <a class="moz-txt-link-abbreviated" href="mailto:melbourne-pm@pm.org">melbourne-pm@pm.org</a>
Subject: Re: [Melbourne-pm] CPAN module
hmm... I was hoping there was something more akin to a 'developer tree'
which would allow updates to a package, but not be part of an
"official" package.
Scott Penrose wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 09/03/2006, at 10:13, Mathew Robertson wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi folks,
I use a CPAN module called HTML::Template, which is used as a
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->web-page
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">templating engine (in a similar vein to Template-Toolkit).
I have made some changes to increase its functionality - which
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->amounts
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">to about 20% of the code (ie: not a small patch). I have suggested
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->that
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">some of these changes be added to the real module, but the developer
isn't interested.
Since I dont really want to do a complete fork of the code, as the
existing community is quite lively... The question is, is there a
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->way
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">to release a modified version into CPAN?
</pre>
</blockquote>
<pre wrap="">No not really, and that would not be fair either - you can't have two
bosses of one bit of code.
But you have already touched on the answer - fork it and release as a
new module.
eg:
HTML::TemplateX
Or maybe
HTML::Template::Extended
Once you do that - and that is fair and safe - you can then encourage
the use of your changes. If the changes are good and acceptable, then
people will use that module instead - eventually it will become the
standard, and probably even get incorporated or replace the old one.
This is not unprecedented - quite common actually :-)
Scott
--* - * <a class="moz-txt-link-freetext" href="http://www.osdc.com.au">http://www.osdc.com.au</a> - Open Source Developers Conference *
</pre>
</blockquote>
<pre wrap=""><!---->- *
</pre>
<blockquote type="cite">
<pre wrap="">Scott Penrose
Open source developer
<a class="moz-txt-link-freetext" href="http://linux.dd.com.au/">http://linux.dd.com.au/</a>
<a class="moz-txt-link-abbreviated" href="mailto:scottp@dd.com.au">scottp@dd.com.au</a>
Dismaimer: Open sauce usually ends up never coming out (of the
</pre>
</blockquote>
<pre wrap=""><!---->bottle).
</pre>
<blockquote type="cite">
<pre wrap="">Please do not send me Word or PowerPoint attachments.
See <a class="moz-txt-link-freetext" href="http://www.gnu.org/philosophy/no-word-attachments.html">http://www.gnu.org/philosophy/no-word-attachments.html</a>
Microsoft is not the answer. It's the question. And the answer is no.
</pre>
</blockquote>
<pre wrap=""><!---->_______________________________________________
Melbourne-pm mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Melbourne-pm@pm.org">Melbourne-pm@pm.org</a>
<a class="moz-txt-link-freetext" href="http://mail.pm.org/mailman/listinfo/melbourne-pm">http://mail.pm.org/mailman/listinfo/melbourne-pm</a>
**********************************************************************
IMPORTANT
The contents of this e-mail and its attachments are confidential and intended
solely for the use of the individual or entity to whom they are addressed. If
you received this e-mail in error, please notify the HPA Postmaster, <a class="moz-txt-link-abbreviated" href="mailto:postmaster@hpa.com.au">postmaster@hpa.com.au</a>,
then delete the e-mail.
This footnote also confirms that this e-mail message has been swept for the
presence of computer viruses by Ironport. Before opening or using any
attachments, check them for viruses and defects.
Our liability is limited to resupplying any affected attachments.
HPA collects personal information to provide and market our services. For more
information about use, disclosure and access see our Privacy Policy at
<a class="moz-txt-link-abbreviated" href="http://www.hpa.com.au">www.hpa.com.au</a>
**********************************************************************
</pre>
</blockquote>
</body>
</html>