|Version 10 (modified by szabgab, 4 years ago) (diff)|
This page should describe (or link to) various process that developers of Padre might want to do. Move stuff from Development to this page or link to that page
Open a Ticket file a bug or a feature request
In order to open a ticket first you need to register on the Trac of Padre. Unfortunately due to excessive spam and our lack of capability to setup SPAM filter we had to disable the registration form and we have to manually enable for every new person. Don't worry though as it is easy to do so. You just have to join us on IRC ( http://padre.perlide.org/irc.html?channel=padre ) (TODO describe IRC more) and ask us to open the registration form for you.
Once registered there is a link to Create Ticket
Setup Development Environment
We recommend first installing a released version of Padre as described on http://padre.perlider.org/download.html and on Download. Once that's working on your system it will be easier to switch to development mode.
In order to develop padre you will need to have a Subversion client.
The URL of our SVN repository is at http://svn.perlide.org/padre/trunk/
It is required to setup a few more utilities to get the developer's environment ready. Specifically you need to install Module::Install and Module::Install::PadrePlugin? from CPAN. See instructions below:
To run Padre from the workspace checked out from SVN type "perl dev.pl"
For Windows we recommend the Tortoise SVN client you can download from http://tortoisesvn.tigris.org/
To install Module::Install open a command prompt and navigate to the folder of the source code (e.g. d:\padre\padre) and type in the following command "cpan Module::Install" (notice: this is case sensitive)
Now you are ready to compile the code you are using. in the same root of your source code tpye "perl Makefile.PL" and press enter Once this finished type "dmake" and press enter
$ cpan Module::Install
Create a Patch
For open source projects (like this one) everyone has read access to the repository, and anyone can make a contribution to the project. So how are those contributions controlled? If just anyone could commit changes, the project would be permanently unstable and probably permanently broken. In this situation the change is managed by submitting a patch file to the development team, who do have write access. They can review the patch first, and then either submit it to the repository or reject it back to the author. Patch files are simply Unified-Diff files showing the differences between your working copy and the base revision.
Prepare your changes according to the guide lines on the Development page
Once your changes are ready you can prepare them for deployment using the following steps: 1) create a patch file 2) attach the patch file to the relevant ticket
Creating a patch file
First you need to make and test your changes. Then instead of using TortoiseSVN → Commit... on the parent folder, you select TortoiseSVN → Create Patch...
you can now select the files you want included in the patch, just as you would with a full commit. This will produce a single file containing a summary of all the changes you have made to the selected files since the last update from the repository.
You can produce separate patches containing changes to different sets of files. Of course, if you create a patch file, make some more changes to the same files and then create another patch, the second patch file will include both sets of changes.
Just save the file using a filename of your choice. Patch files can have any extension you like, in our project you should use the .patch extension. The file name should look like <my_patch_file_name.patch>. You are now ready to submit your patch file.
You can also save the patch to the clipboard instead of to a file. You might want to do this so that you can paste it into “past bin” http://pastebin.com for review by others. Or if you have two working copies on one machine and you want to transfer changes from one to the other, a patch on the clipboard is a convenient way of doing this.
Submitting the patch file
Submitting a patch in the padre project simply means attaching the patch file created to a Ticket.
Find the relevant ticket in Trac and attach the patch file you created to that Ticket. If you fixed something which did not have an open ticket you should first open a ticket and then attach the patch file.
The patch file will be reviewed by an authorized developer who will either apply the patch or get in touch (usually on IRC http://webchat.perl.org/?channels=padre) with the person submitting the fix to discuss any issues
We have a separate page for people who would like to get involved in the translation of Padre. See TranslationIntro
Improve the Web site of Padre
There are a number of tickets open for improving the web site: report:11 In addition you are welcome to open your own tickets.
The web site of Padre is partially built using Template Toolkit and partially relies on Trac. Everything in the http://padre.perlide.org/trac is under Trac or generated by trac from the SVN repository.
The source of the rest of the web site can be found in SVN in http://svn.perlide.org/padre/trunk/template.padre.perlide.org/
In order to make changes to the website you will have to
- Check out the source from SVN
- Install the necessary perl modules (try running perl Build.PL in the checked out directory
- Make changes
- Build the web site on your machine so you can see if your changes were good
- Send a patch or commit to svn if you got a commit bit
Release, packaging and Distribution
How to run Padre from a GNOME launcher
Using padre in a GNOME launcher doesn't work in case the Perl modules needed by Padre are installed in a user specific directory, for example by using local::lib. A simple workaround is to create a bash script which uses local::lib (or sets the PERL5LIB environment variable by some other means) and then calls padre:
#!/bin/bash eval $(perl -I$HOME/perl5/lib/perl5 -Mlocal::lib) /home/ahartmai/perl5/bin/padre >/tmp/padre_out 2>/tmp/padre_err
TODO: improve the details here