1. Dependency Management
With Pinto
Jeffrey Thalhammer
thaljef@cpan.org
YAPC::NA
June 15, 2012

2. CPAN Is Heaven
Tens of thousands of
modules for every
purpose imaginable
Lots of ser vices for
testing, bug tracking,
ratings, forums
Awesome tool chain
for building, testing,
installing

3. CPAN Is Hell
The CPAN is not
stable
Developers
constantly adding
and removing stuff
Sometimes the code
is broken
Tool chain expects
backward
compatibility

4. Unintended Consequences
Avoiding
dependencies
Avoiding upgrades
Shared resources &
monolithic systems
Unreproducible
environments

5. Combating The Problem
“Just stash the site_perl directory in the VCS”
Brittle
Not portable
Can’t smoke it
Hard to evolve

6. Combating The Problem
“Just stash the distribution tarballs in the VCS”
Slightly less brittle
Portable
Smokable
Still icky

7. CPAN::Site & CPAN::Mini
• Snapshots of the CPAN
• Solves the stability problem
• Still clunky

8. More Shops Are Writing CPAN-
style Dists
• M::B
and EU::MM more
commonplace
• Dist::Zilla
makes the
development fun
• cpanmmakes the
deployment easy
• DarkPANs proliferate

9. Lots of DarkPAN Tools Emerge
• CPAN::Mini::Inject
• MyCPAN::App::DPAN
• CPAN::Dark
• OrePAN

10. Pinto Is Born
Had built 3 private
CPANS
Always required some
hacks
Not happy with the
result
Started form scratch

11. What is Pinto?
An extensible tool for managing
dependencies via a CPAN-like repository

12. Context
You have an app called My-App
The app contains package My::App
The app requires URI (latest is 1.59)

13. Creating A Repository

14. Creating A Repository
pinto --root=~/mypan init

15. Creating A Repository
pinto --root=~/mypan init
path to the repository

16. Creating A Repository
pinto --root=~/mypan init
“init” command

17. Creating A Repository
pinto --root=~/mypan init

18. Inspecting The Repository
pinto --root=~/mypan list

19. Inspecting The Repository
pinto --root=~/mypan list
“list” command

20. Inspecting The Repository
pinto --root=~/mypan list
path to the repository

21. Inspecting The Repository
pinto --root=~/mypan list

22. A Shortcut
pinto --root=~/mypan list

23. A Shortcut
pinto --root=~/mypan list
pinto -r ~/mypan list

24. A Shortcut
pinto --root=~/mypan list
pinto -r ~/mypan list
export PINTO_REPOSITORY_ROOT=~/mypan

25. A Shortcut
pinto --root=~/mypan list
pinto -r ~/mypan list
export PINTO_REPOSITORY_ROOT=~/mypan
pinto list

26. Fetching Dependencies

27. Fetching Dependencies
pinto pull URI

28. Fetching Dependencies
pinto pull URI
“pull” command

29. Fetching Dependencies
pinto pull URI
package name

30. Fetching Dependencies
pinto pull URI

31. What Did We Get?

32. What Did We Get?
pinto list

33. What Did We Get?
pinto list
rf URI 1.59 GAAS/URI-1.59.tar.gz
rf URI::Escape 3.31 GAAS/URI-1.59.tar.gz
rf URI::Heuristic 4.20 GAAS/URI-1.59.tar.gz
rf URI::IRI 0 GAAS/URI-1.59.tar.gz
rf URI::QueryParam 0 GAAS/URI-1.59.tar.gz
rf URI::Split 0 GAAS/URI-1.59.tar.gz
...

34. Understanding The Listing
rf URI 1.59 GAAS/URI-1.59.tar.gz

35. Understanding The Listing
rf URI 1.59 GAAS/URI-1.59.tar.gz
“r” means release dist

36. Understanding The Listing
rf URI 1.59 GAAS/URI-1.59.tar.gz
“f” means a foreign dist

37. Understanding The Listing
rf URI 1.59 GAAS/URI-1.59.tar.gz
The package name

38. Understanding The Listing
rf URI 1.59 GAAS/URI-1.59.tar.gz
The package version number

39. Understanding The Listing
rf URI 1.59 GAAS/URI-1.59.tar.gz
The distribution’s author ID

40. Understanding The Listing
rf URI 1.59 GAAS/URI-1.59.tar.gz
The distribution archive

41. Understanding The Listing
rf URI 1.59 GAAS/URI-1.59.tar.gz

42. Injecting Your Own Distribution

43. Injecting Your Own Distribution
pinto add some/dir/My-App-1.0.tar.gz

44. Injecting Your Own Distribution
pinto add some/dir/My-App-1.0.tar.gz
“
add” command

45. Injecting Your Own Distribution
pinto add some/dir/My-App-1.0.tar.gz
Path to local dist archive

46. Injecting Your Own Distribution
pinto add some/dir/My-App-1.0.tar.gz

47. Injecting Your Own Distribution
pinto add some/dir/My-App-1.0.tar.gz
pinto list

48. Injecting Your Own Distribution
pinto add some/dir/My-App-1.0.tar.gz
pinto list
rl My::App 1.0 YOU/My-App-1.0.tar.gz
rf URI 1.59 GAAS/URI-1.59.tar.gz
rf URI::Escape 3.31 GAAS/URI-1.59.tar.gz
...

49. Installing With cpan
$ cpan
cpan[1]> o conf urllist file://$HOME/mypan
cpan[2]> install My::App

50. Installing With cpan
$ cpan
cpan[1]> o conf urllist file://$HOME/mypan
cpan[2]> install My::App
point to your repository

51. Installing With cpan
$ cpan
cpan[1]> o conf urllist file://$HOME/mypan
cpan[2]> install My::App

52. Installing With cpanm

53. Installing With cpanm
cpanm --mirror file://$HOME/mypan
--mirror-only My::App

54. Installing With cpanm
cpanm --mirror file://$HOME/mypan
--mirror-only My::App
point to your repository

55. Installing With cpanm
cpanm --mirror file://$HOME/mypan
--mirror-only My::App
do not fall back to CPAN

56. Installing With cpanm
cpanm --mirror file://$HOME/mypan
--mirror-only My::App

57. Installing With pinto

58. Installing With pinto
pinto install My::App

59. Installing With pinto
pinto install My::App
“install” command

60. Installing With pinto
pinto install My::App

61. Upgrading Dependencies

62. Upgrading Dependencies
pinto pull URI~1.60

63. Upgrading Dependencies
pinto pull URI~1.60
“pull” command

64. Upgrading Dependencies
pinto pull URI~1.60
Package name and minimum version

65. Upgrading Dependencies
pinto pull GAAS/URI-1.60.tar.gz

66. Upgrading Dependencies
pinto pull GAAS/URI-1.60.tar.gz
pinto list

67. Upgrading Dependencies
pinto pull GAAS/URI-1.60.tar.gz
pinto list
rl My::App 1.0 YOU/My-App-1.0.tar.gz
rf URI 1.60 GAAS/URI-1.60.tar.gz
rf URI::Escape 3.32 GAAS/URI-1.60.tar.gz
rf URI::Heuristic 4.20 GAAS/URI-1.60.tar.gz
...

68. Working With Stacks

69. What Is A Stack?
A named mapping from package
names to distribution archives
Conceptually equivalent to the
02packages.details.txt file
In a CPAN, there is only one
“stack”, and it usually contains
only latest package versions
But a Pinto repository can have
multiple stacks, that contain
arbitrary package versions

70. The Default Stack
Every Pinto repository has a
built-in stack called “init”
It is the default stack for all
operations
You can change the default
stack

71. Creating A Stack

72. Creating A Stack
pinto new upgrades

73. Creating A Stack
pinto new upgrades
“new” command

74. Creating A Stack
pinto new upgrades
stack name

75. Creating A Stack
pinto new upgrades
pinto copy init upgrades

76. Creating A Stack
pinto new upgrades
pinto copy init upgrades
“copy” command

77. Creating A Stack
pinto new upgrades
pinto copy init upgrades
from stack

78. Creating A Stack
pinto new upgrades
pinto copy init upgrades
to stack

79. Creating A Stack
pinto new upgrades
pinto copy init upgrades

80. Upgrading On A Stack
pinto pull --stack=upgrades URI~1.62

81. Upgrading On A Stack
pinto pull --stack=upgrades URI~1.62
“pull” command

82. Upgrading On A Stack
pinto pull --stack=upgrades URI~1.62
specify the stack name

83. Upgrading On A Stack
pinto pull --stack=upgrades URI~1.62
package name and version

84. Upgrading On A Stack
pinto pull --stack=upgrades URI~1.62

85. Upgrading On A Stack
pinto pull --stack=upgrades URI~1.62
pinto list --stack=upgrades

86. Upgrading On A Stack
pinto pull --stack=upgrades URI~1.62
pinto list --stack=upgrades
specify the stack name

87. Upgrading On A Stack
pinto pull --stack=upgrades URI~1.62
pinto list --stack=upgrades
rl My::App 1.0 YOU/My-App-1.0.tar.gz
rf URI 1.62 GAAS/URI-1.62.tar.gz
rf URI::Escape 3.32 GAAS/URI-1.62.tar.gz
rf URI::Heuristic 4.20 GAAS/URI-1.62.tar.gz
...

88. Looking Across Stacks
pinto list --stack=@ -P=URI

89. Looking Across Stacks
pinto list --stack=@ -P=URI
special stack “
@”

90. Looking Across Stacks
pinto list --stack=@ -P=URI
only packages matching %URI%

91. Looking Across Stacks
pinto list --stack=@ -P=URI
rf init URI 1.60 GAAS/URI-1.60.tar.gz
rf upgrades URI 1.62 GAAS/URI-1.62.tar.gz
...

92. Installing From A Stack
pinto install --stack=upgrades My::App

93. Installing From A Stack
pinto install --stack=upgrades My::App
“install” command

94. Installing From A Stack
pinto install --stack=upgrades My::App
specify stack name

95. Installing From A Stack
pinto install --stack=upgrades My::App
package name

96. Installing From A Stack
pinto install --stack=upgrades My::App

97. Merging Stacks
pinto merge upgrades init

98. Merging Stacks
pinto merge upgrades init
“merge” command

99. Merging Stacks
pinto merge upgrades init
from stack

100. Merging Stacks
pinto merge upgrades init
to stack

101. Merging Stacks
pinto merge upgrades init

102. Merging Stacks
pinto merge upgrades init
rf init URI 1.62 GAAS/URI-1.62.tar.gz
rf upgrades URI 1.62 GAAS/URI-1.62.tar.gz
...

103. Why Use Stacks?
• Stacks for upgrades
• Stacks for each feature
• Stacks for dev/qa/prod
• Stacks for each product
• Stacks for each perl version
• Stacks for each customer

104. Working With Pins

105. What Is A Pin?
Fixes a particular
package & version to
stack
Cannot be upgraded
or downgraded
Until you unpin it

106. Pinning A Package
pinto pin URI

107. Pinning A Package
pinto pin URI
“pin” command

108. Pinning A Package
pinto pin URI
package name

109. Pinning A Package
pinto pin URI

110. Pinning A Package
pinto pin URI
pinto list

111. Pinning A Package
pinto pin URI
pinto list
rf+ URI 1.59 GAAS/URI-1.59.tar.gz
rf+ URI::Escape 3.31 GAAS/URI-1.59.tar.gz
rf+ URI::Heuristic 4.20 GAAS/URI-1.59.tar.gz

112. Pinning A Package
pinto pin URI
pinto list
rf+ URI 1.59 GAAS/URI-1.59.tar.gz
rf+ URI::Escape 3.31 GAAS/URI-1.59.tar.gz
rf+ URI::Heuristic 4.20 GAAS/URI-1.59.tar.gz
“+” indicates a pin

113. Pinning A Package
pinto pin URI
pinto list
rf+ URI 1.59 GAAS/URI-1.59.tar.gz
rf+ URI::Escape 3.31 GAAS/URI-1.59.tar.gz
rf+ URI::Heuristic 4.20 GAAS/URI-1.59.tar.gz

114. Pinning A Package

115. Pinning A Package
Suppose you want to use Catalyst

116. Pinning A Package
Suppose you want to use Catalyst
And Catalyst requires Plack 0.99

117. Pinning A Package
Suppose you want to use Catalyst
And Catalyst requires Plack 0.99
And Plack 0.99 requires HTTP::Request 6.03

118. Pinning A Package
Suppose you want to use Catalyst
And Catalyst requires Plack 0.99
And Plack 0.99 requires HTTP::Request 6.03
And HTTP::Request requires ...

119. Pinning A Package
Suppose you want to use Catalyst
And Catalyst requires Plack 0.99
And Plack 0.99 requires HTTP::Request 6.03
And HTTP::Request requires ...
...requires URI 1.62

120. Pinning A Package
pinto -v pull Catalyst

121. Pinning A Package
pinto -v pull Catalyst
Pulling Catalyst-Runtime-5.90012.tar.gz

122. Pinning A Package
pinto -v pull Catalyst
Pulling Catalyst-Runtime-5.90012.tar.gz
Pulling CGI-Simple-1.113.tar.gz

123. Pinning A Package
pinto -v pull Catalyst
Pulling Catalyst-Runtime-5.90012.tar.gz
Pulling CGI-Simple-1.113.tar.gz
...

124. Pinning A Package
pinto -v pull Catalyst
Pulling Catalyst-Runtime-5.90012.tar.gz
Pulling CGI-Simple-1.113.tar.gz
...
Pulling Plack-0.9988.tar.gz

125. Pinning A Package
pinto -v pull Catalyst
Pulling Catalyst-Runtime-5.90012.tar.gz
Pulling CGI-Simple-1.113.tar.gz
...
Pulling Plack-0.9988.tar.gz
Pulling Devel-StackTrace-1.27.tar.gz

126. Pinning A Package
pinto -v pull Catalyst
Pulling Catalyst-Runtime-5.90012.tar.gz
Pulling CGI-Simple-1.113.tar.gz
...
Pulling Plack-0.9988.tar.gz
Pulling Devel-StackTrace-1.27.tar.gz
...

127. Pinning A Package
pinto -v pull Catalyst
Pulling Catalyst-Runtime-5.90012.tar.gz
Pulling CGI-Simple-1.113.tar.gz
...
Pulling Plack-0.9988.tar.gz
Pulling Devel-StackTrace-1.27.tar.gz
...
Pulling HTTP-Message-6.03.tar.gz

128. Pinning A Package
pinto -v pull Catalyst
Pulling Catalyst-Runtime-5.90012.tar.gz
Pulling CGI-Simple-1.113.tar.gz
...
Pulling Plack-0.9988.tar.gz
Pulling Devel-StackTrace-1.27.tar.gz
...
Pulling HTTP-Message-6.03.tar.gz
Pulling URI-1.62

129. Pinning A Package
pinto -v pull Catalyst
Pulling Catalyst-Runtime-5.90012.tar.gz
Pulling CGI-Simple-1.113.tar.gz
...
Pulling Plack-0.9988.tar.gz
Pulling Devel-StackTrace-1.27.tar.gz
...
Pulling HTTP-Message-6.03.tar.gz
Pulling URI-1.62
Cannot add GAAS/URI-1.62/URI~1.62 to stack init
because URI is pinned to GAAS/URI-1.59/URI~1.59

130. Why Pin?

131. Why Pin?
Prevent other
developers from
upgrading directly

132. Why Pin?
Prevent other
developers from
upgrading directly
Prevent other
dependencies from
upgrading directly

133. Using Pins And Stacks
Together

134. Experiment With Upgrades

135. Experiment With Upgrades
You have a “prod” stack with DBIx::Class 1.6

136. Experiment With Upgrades
You have a “prod” stack with DBIx::Class 1.6
Make a copy of the “prod” stack called “test”

137. Experiment With Upgrades
You have a “prod” stack with DBIx::Class 1.6
Make a copy of the “prod” stack called “test”
Upgrade to DBIx::Class 1.7 on “test” stack

138. Experiment With Upgrades
You have a “prod” stack with DBIx::Class 1.6
Make a copy of the “prod” stack called “test”
Upgrade to DBIx::Class 1.7 on “test” stack
Build & test application using the “test” stack

139. Experiment With Upgrades
You have a “prod” stack with DBIx::Class 1.6
Make a copy of the “prod” stack called “test”
Upgrade to DBIx::Class 1.7 on “test” stack
Build & test application using the “test” stack
If the tests fail pin DBIx::Class on the “prod” stack

140. Making Local Patches

141. Making Local Patches
You find a bug in Plack-0.98

142. Making Local Patches
You find a bug in Plack-0.98
You patch and re-package as Plack-0.98_01.tar.gz

143. Making Local Patches
You find a bug in Plack-0.98
You patch and re-package as Plack-0.98_01.tar.gz
Put Plack-0.98_01.tar.gz in the “prod” stack

144. Making Local Patches
You find a bug in Plack-0.98
You patch and re-package as Plack-0.98_01.tar.gz
Put Plack-0.98_01.tar.gz in the “prod” stack
Pin Plack on the “prod” stack

145. Making Local Patches
You find a bug in Plack-0.98
You patch and re-package as Plack-0.98_01.tar.gz
Put Plack-0.98_01.tar.gz in the “prod” stack
Pin Plack on the “prod” stack
Remove pin when the author fixes bug

146. Making Local Patches
You find a bug in Plack-0.98
You patch and re-package as Plack-0.98_01.tar.gz
Put Plack-0.98_01.tar.gz in the “prod” stack
Pin Plack on the “prod” stack
Remove pin when the author fixes bug
Pull Plack-0.99 into the “prod” stack

147. Pinto In The Real World

148. Pinto And Legacy Code

149. Pinto And Legacy Code
Don’t always know what has been installed.
So use Dist::Sur veyor to discover dependencies.
Stash dependency list in a text file.
Then feed dependencies into a Pinto repository.

150. Pinto And Legacy Code
Don’t always know what has been installed.
So use Dist::Sur veyor to discover dependencies.
Stash dependency list in a text file.
Then feed dependencies into a Pinto repository.
pinto pull --norecurse < dependencies.txt

151. Pinto And Legacy Code
Don’t always know what has been installed.
So use Dist::Sur veyor to discover dependencies.
Stash dependency list in a text file.
Then feed dependencies into a Pinto repository.
pinto pull --norecurse < dependencies.txt
do not automatically fetch deps

152. Pinto And Legacy Code
Don’t always know what has been installed.
So use Dist::Sur veyor to discover dependencies.
Stash dependency list in a text file.
Then feed dependencies into a Pinto repository.
pinto pull --norecurse < dependencies.txt

153. Pinto And Dist::Zilla

154. Pinto And Dist::Zilla
dzil listdeps | pinto pull

155. Pinto And Dist::Zilla
dzil listdeps | pinto pull
dzil authordeps | pinto pull

156. Pinto And The Development Cycle

157. Pinto And The Development Cycle
Usually don’t know dependencies ahead of time.

158. Pinto And The Development Cycle
Usually don’t know dependencies ahead of time.
Might install several modules before choosing.

159. Pinto And The Development Cycle
Usually don’t know dependencies ahead of time.
Might install several modules before choosing.
This process might take several days or weeks.

160. Pinto And The Development Cycle
Usually don’t know dependencies ahead of time.
Might install several modules before choosing.
This process might take several days or weeks.
By the time we decide, CPAN might changed.

161. Pinto And The Development Cycle
Usually don’t know dependencies ahead of time.
Might install several modules before choosing.
This process might take several days or weeks.
By the time we decide, CPAN might changed.
So there’s a hole in the development process.

162. Pinto And The Development Cycle
pinto install -L ~/myperl5 --pull Catalyst

163. Pinto And The Development Cycle
pinto install -L ~/myperl5 --pull Catalyst
“install” command

164. Pinto And The Development Cycle
pinto install -L ~/myperl5 --pull Catalyst
install into local::lib

165. Pinto And The Development Cycle
pinto install -L ~/myperl5 --pull Catalyst
package name

166. Pinto And The Development Cycle
pinto install -L ~/myperl5 --pull Catalyst
awesome --pull flag

167. Pinto And The Development Cycle
pinto install -L ~/myperl5 --pull Catalyst

168. Pinto And The Development Cycle
pinto install -L ~/myperl5 --pull Catalyst
First, pulls Catalyst and any missing
dependencies into the repository.

169. Pinto And The Development Cycle
pinto install -L ~/myperl5 --pull Catalyst
First, pulls Catalyst and any missing
dependencies into the repository.
Dependencies must not violate pin constraints
or command fails before installing anything.

170. Pinto And The Development Cycle
pinto install -L ~/myperl5 --pull Catalyst
First, pulls Catalyst and any missing
dependencies into the repository.
Dependencies must not violate pin constraints
or command fails before installing anything.
Then, installs Catalyst and dependencies (from
the repository) into your local::lib directory.

171. Gotchas
Pinto does not index exactly like PAUSE
May not work for old or oddly packaged code
Pinto does not enforce permissions
Pinto is strict about version numbers

172. Pinto And Teamwork
Repository on shared storage area
Easy to setup
Performance may suck on NFS
Usual permission issues

173. Pinto And Teamwork
Repository on a remote host via HTTP
pintod on remote host
pinto on local host
Can utilize fast storage
Can use HTTP authentication

174. Running pintod
remotehost

175. Running pintod
remotehost
pinto --root=/var/ourpan init

176. Running pintod
remotehost
pinto --root=/var/ourpan init
pintod --root=/var/ourpan

177. Running pintod
remotehost
pinto --root=/var/ourpan init
pintod --root=/var/ourpan
localhost

178. Running pintod
remotehost
pinto --root=/var/ourpan init
pintod --root=/var/ourpan
localhost
pinto --root=http://somehost COMMAND

179. Using pintod For Installation

180. Using pintod For Installation
$ cpan
cpan[1]> o conf urllist http://remotehost/dev
cpan[2]> install My::App

181. Using pintod For Installation
$ cpan
cpan[1]> o conf urllist http://remotehost/dev
cpan[2]> install My::App
append stack name to url

182. Using pintod For Installation
$ cpan
cpan[1]> o conf urllist http://remotehost/dev
cpan[2]> install My::App
cpanm --mirror http://remotehost/dev
--mirror-only My::App

183. Using pintod For Installation
$ cpan
cpan[1]> o conf urllist http://remotehost/dev
cpan[2]> install My::App
cpanm --mirror http://remotehost/dev
--mirror-only My::App
append stack name to url

184. Using pintod For Installation
$ cpan
cpan[1]> o conf urllist http://remotehost/dev
cpan[2]> install My::App
cpanm --mirror http://remotehost/dev
--mirror-only My::App
pinto --root=http://remotehost install
--stack=dev My::App

185. Using pintod For Installation
$ cpan
cpan[1]> o conf urllist http://remotehost/dev
cpan[2]> install My::App
cpanm --mirror http://remotehost/dev
--mirror-only My::App
pinto --root=http://remotehost install
--stack=dev My::App
point to pinto ser ver

186. Using pintod For Installation
$ cpan
cpan[1]> o conf urllist http://remotehost/dev
cpan[2]> install My::App
cpanm --mirror http://remotehost/dev
--mirror-only My::App
pinto --root=http://remotehost install
--stack=dev My::App
specify the stack

187. Using pintod For Installation
$ cpan
cpan[1]> o conf urllist http://remotehost/dev
cpan[2]> install My::App
cpanm --mirror http://remotehost/dev
--mirror-only My::App
pinto --root=http://remotehost install
--stack=dev My::App

188. Pinto Net works

189. Pinto Net works
CPAN succeeds because it is
centralized

190. Pinto Net works
CPAN succeeds because it is
centralized
CPAN fails because it is
centralized

191. Pinto Net works
CPAN succeeds because it is
centralized
CPAN fails because it is
centralized
Pinto can be centralized or
distributed

192. Pinto Net works
The CPAN
Team Team
1 3
Team
2

193. Pinto Net works

194. Pinto Net works
Might not be a good idea

195. Pinto Net works
Might not be a good idea
No obvious way to resolve
namespace conflicts

196. Pinto Net works
Might not be a good idea
No obvious way to resolve
namespace conflicts
We’ll have to wait and see
if this pans out

197. Pinto And OS Packaging
• UsePinto to build up your
application in some
directory
• Packagethe directory with
your favorite OS tools
• Add dependencies on non-
perl stuff
• Deploy as usual

198. Pinto And Other Tools
• Still
just a pile of directories
and files with an index
• AnnoCPAN, MetaCPAN,
CPAN::Mini::Webser ver, etc.
should still work

199. Pinto versus Carton
Pinto Carton
Light weight
VCS-Friendly
Local Patches
Stack Support
Enterprise
Strength

200. Some Odds & Ends
• Dist::Zilla::Plugin::Pinto::Add - release your dist to a
Pinto repository with dzil
• Dist::Zilla::Chef
- use Pinto to manage your project
dependencies within the dzil workflow

201. Pinto Architecture
Pinto
Configuration
Pull Add Copy Merge
Logging
Repository
Database File Store

202. Extending Pinto
• Create
an Action subclass and override the “execute”
method
• YourAction has access to the configuration, logger, and
repository objects
• Your Action can do whatever it wants
• Like extract POD or ack source code in a distribution
• But the API is not really stable yet

203. Future Plans
More VCS-behaviors: revert, diffs
Report upstream impacts of upgrades
Check stack for unsatisfiable dependencies
Visualize dependency graphs
Faster

204. Get Yours Today
https://metacpan.org/module/Pinto
https://github.com/thaljef/Pinto

205. Thanks For Your Time
Jeffrey Thalhammer
thaljef@cpan.org