svn externals and perl packages

nmerriweather has asked for the wisdom of the Perl Monks concerning the following question:

has anyone been using svn externals for custom perl packages?
i'm in this situation:

repository a
myPackage/trunk/
myPackage/trunk/myPackage.pm
myPackage/trunk/myPackage/ #
[download]

repository b
myWebApp/trunk/
myWebApp/trunk/lib/
myWebApp/trunk/lib/myPackage.pm
myWebApp/trunk/lib/myPackage/
[download]

if you don't follow... i have a repsoitory for a shared package that i use across several webapps.

right now, i just copy the package into each webapp. i'd like to use svn:externals - actually , I'd LOVE to use externals, but externals only works on files, not folders. perl package namespace has the layout

package.pm #file
package/ #folder
[download]

so i haven't figured out a way to let me use my own perl packages as svn externals. does anyone have a clue?

Comment on svn externals and perl packages Select or Download Code

Replies are listed 'Best First'.
Re: svn externals and perl packages by runrig (Abbot) on Jun 08, 2006 at 00:04 UTC
If either all of your modules that go into /lib are in the same repository, or if you restructure your custom modules so that every .pm file is in a subdirectory of /lib (e.g. transform myPackage into My::Package throughout the code, with all My:: modules in the same repository), then using externals would be straightforward.	[reply]
Re: svn externals and perl packages by Anonymous Monk on Jun 07, 2006 at 04:33 UTC
but externals only works on files, not folders. perl package namespace has the layout No. RTFM http://svnbook.red-bean.com/en/1.0/ch07s03.html	[reply]
A reply falls below the community's threshold of quality. You may see it by logging in.
A reply falls below the community's threshold of quality. You may see it by logging in.