Re: Improved Subversion guide
Julian Mehnle wrote:
> I wrote:
>> I wrote:
>>> [...] Also, I see that the pkg-perl group's Subversion guide
>>> (/website/subversion.pod) has a gap in the description of how to
>>> upgrade to new upstream versions. Having learned today how that works,
>>> I volunteer to fill in that section if nobody objects.
>> First, I rewrapped and cleaned up subversion.pod. Then I made the
>> following substantial changes:
>> * Filled in the missing parts and section 6 for upstream upgrades.
>> * Don't explain implicit tagging using `svn-buildpackage --svn-tag`,
>> as tagging is already explained in section 5, "Tagging and Releasing". *
>> Explain how to make svn-buildpackage lintian-check the built package.
>>
>> I however don't have the slightest clue how to install an updated
>> subversion.html to the actual website -- I most likely don't even have
>> the needed privileges, so someone else will have probably to do it.
>
> Well, nearly a month passed. What exactly needs to be done to bring the
> Subversion guide displayed on the website[1] up to date with the POD in
> the Svn repo?
eloy@ws143:~$ scp website/subversion.pod pkg-perl.alioth.debian.org:
(go to pkg-perl.alioth.debian.org)
eloy@haydn:~$ cp subversion.pod
/var/lib/gforge/chroot/home/groups/pkg-perl/htdocs/
eloy@haydn:~$ cd /var/lib/gforge/chroot/home/groups/pkg-perl/htdocs/
eloy@haydn:/var/lib/gforge/chroot/home/groups/pkg-perl/htdocs$ pod2html
subversion.pod > subversion.html
AFAIR everyone from pkg-perl is able to do that.
Please check is file is up to date now.
eloy
--
-------e-l-o-y---------------------------e-l-o-y-@-k-o-f-e-i-n-a-.-n-e-t------
jak to dobrze, że są oceany - bez nich byłoby jeszcze smutniej
Reply to: