Changes between Version 1 and Version 2 of Distribution
- Timestamp:
- 09/08/09 11:55:16 (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Distribution
v1 v2 1 [[PageOutline(1-2)]] 2 3 = Packaging and Distribution = 4 5 The primary distribution channel of Padre and the plugins is CPAN. 6 Hence for every release first we create a CPAN distribution of Padre 7 or the plugin and upload it to CPAN. (See the [wiki:Release] page for details). 8 9 1 10 == Distribution of Padre == 2 11 3 The primary distribution channel of Padre is CPAN. Hence for every release first we create a CPAN distribution of Padre. (See the [wiki:Release] page on how). 12 == Linux/Unix/BSD downstream distributions == 4 13 5 Based on the CPAN package the downstream distributors (Debian, Fedora, Mandriva, FreeBSD etc.) create their .deb, .rpm etc. files. 6 The [wiki:Download] page contains information about the people who maintain those packages in those distribution and the status. 14 Based on the CPAN package the downstream distributors (Debian, Fedora, Mandriva, FreeBSD etc.) 15 create their .deb, .rpm etc. files. 16 The [wiki:Download] page contains information about the people who 17 maintain those packages in those distribution and the status. 18 19 == Linux/Unix/BSD downloadable exe == 20 21 There is a plan to create a module called Dist::Perl::XL which would create 22 a full version of perl with Padre (and possibly other things) installed and zipped. 23 Users will be able to download it, unzip it and run padre from that perl. 24 They will be able to use either the perl that came with Padre 25 or any other perl as their 'production perl'. 26 Primarily we try to make this work for Linux. 27 28 == Linux/Unix/BSD downloadable exe based on PAR == 29 30 #399 represents a bug. For now we have stopped the resarch in this direction. 31 32 == Linux/Unix/BSD installatio based on Shipwright == 33 34 There is a project on Github attempting to create a Shipwright 35 package for Padre: https://github.com/garu/shipwright-padre 36 Ask garu for the current situation. 37 38 == Windows ActivePerl == 39 40 We used to build ppm packages for Padre but we stopped it a long time ago 41 mostly for lazyness. You are welcome to help renewing the effort though 42 it would be probably better to make sure the build system of Activestate 43 can handle it. See #508 for details. 7 44 8 45 9 46 10 For Windows: 47 == Windows Stand alone == 48 49 11 50 12 51 There is a Dist::Perl::Padre in the works that will allow us to create a Perl distribution that has padre already installed. … … 14 53 That will mean the 'production perl' of the user and the perl needed by Padre does not need to be the same. 15 54 16 For Linux/Unix/BSD:17 55 18 There is a plan to create a Dist::Perl::XL which would be a full version of perl with Padre (and possibly other things) installed and zipped. 19 Users will be able to download it, unzip it and run padre from that perl. They will be able to use either the perl that came with Padre 20 or any other perl as their 'production perl'. 21 Primarily we try to make this work for Linux. 22 23 For Mac: 56 == Mac == 24 57 25 58 No idea. Maybe the above Dist::Perl::XL will work there too. … … 29 62 issue that currently stops us (ORLite::Migrate and PAR not working well together) See #294 and #399 30 63 31 == Distribution of the plugins == 64 65 66 == Plugins == 32 67 33 68 Some of the plugins will be distributed by the downstream distributors and/or will be packaged in the Dist::Perl::Padre 34 69 and Dist::Perl::XL distributions. Others will be able to be either installed from CPAN or will be packaged as PAR packages. 35
