-
Notifications
You must be signed in to change notification settings - Fork 10
/
Copy pathBUILD
57 lines (39 loc) · 1.65 KB
/
BUILD
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
To build a distribution kit:
Clone the git repository & cd to it
Make any changes.
Make sure any executables are marked properly in the index:
git update-index --chmod +x file
Make sure any binary or special line-ending files are on .gitignore
Commit any changes.
Install Dist::Zilla from CPAN (has many dependencies, takes a LONG time)
Install Dist::Zilla::Plugin::CopyFilesFromBuild
Install Dist::Zilla::Plugin::MakeMaker::Awesome
Install Dist::Zilla::Plugin::MetaProvides::Package
Install Dist::Zilla::Plugin::MinimumPerl
Install Dist::Zilla::Plugin::Run
Install Dist::Zilla::Plugin::Signature # If you plan to sign your distributions.
# Otherwise, comment-out the [Signature] in dist.ini
Install Pod::Readme
Update the version number in lib/PKCS10.pm (and Changes)
Make any README changes in lib/PKCS10.pm
Update copyrights.
Update Changes
Update dist.ini [Encoding] if any new binary file types are packaged.
Run build:
dzil build [--trial]
The output is Crypt-PKCS10-<version>/ and .tar.gz
README, Commitlog, LICENSE, Makefile.PL, MANIFEST, META.* are auto-generated by the build.
Test the distribution:
dzil test
perlbrew exec prove -vl
Check to make sure that no extra files were included - update dist.ini if so.
tar -tzf <dist>.tgz | sort | less
Note that build doesn't empty the build directory (a Dist::Zilla bug)
To Release
dzil release --trial
or
dzil release
This will make a few changes, including updating the README and in META updating the release type.
Commit those changes as "Release version ..."
Tag that commit.
Note that the Commitlog (file) in the distribution is never committed to git.