-=| Peter Lavender, Tue, Jun 22, 2010 at 07:31:15PM +1000 |=-
> On Mon, 2010-06-21 at 13:39 +0300, Damyan Ivanov wrote:
> > -=| Peter Lavender, Mon, Jun 21, 2010 at 07:32:54PM +1000 |=-
> > > So how do we keep that up to date?
> > 
> > That's package maintainer's job. I.e. mine and Ryan's.
> > 
> > Currently we are missing only 0.64, which is not that bad, I think.
> 
> No, not bad at all.  It's bad on my behalf as I didn't see the version
> number padre was at.

No harm done. I am not very happy with my commitments to padre 
packaging, so I am sure things can be improved.

> > Co-maintainers are welcome, though. Interested parties should get 
> > an account on alioth.debian.org (the debian GForge instance) and 
> > ask to join the pkg-perl project. Then clone 
> > ssh://git.debian.org/git/pkg-perl/apps/padre.git and follow the 
> > instructions in debian/README.source.
> 
> I gather by this and the fact that I've been asked for a password you
> don't have an open repo to download from?

Ah, replace 'ssh' with 'git' and you can clone that. There is also 
a web frontend at http://git.debian.org/?p=pkg-perl/apps/padre.git

Other developer information about the package is available at 
http://packages.qa.debian.org/padre

If you happen to run Debian, you can get a clone of the repository by 
running 'debcheckout $package'. 'debcheckout' is in the devscripts 
package.

> I was just hoping to pull the repo and have a look around to see 
> what's
> required in managing such a thing.

So far the hardest part has been getting the new dependencies packaged 
(not much lately, though) and reviewing the diff.

> I think there are a few
> Padre-Plugins that might do with some work getting them included.

Each plugin is packaged separately. You can see them as 'Other hits' 
when searching for padre: http://packages.debian.org/padre

To see their repositories, follow the link for 'sid (unstable)' and 
then click 'Developer infomation (PTS)' link at the right panel. The 
page that opens has links to the repository URL (for cloning/checking 
out) and a link to the web frontend ('VCS' at left).

Hopefuly this gives enough clues. Admittedly the information is 
scatterred, but since there is lots of it, it was split into parts 
interesting to users, and developer parts.

Attachment: signature.asc
Description: Digital signature

_______________________________________________
Padre-dev mailing list
Padre-dev@perlide.org
http://mail.perlide.org/mailman/listinfo/padre-dev

Reply via email to