# from David Golden
# on Monday 26 January 2009 14:37:
>It's just not clear what the hell I do with it. Make a config file of
>some sort, right? What do I put into it? Why one thing or another? Do
>I have to hand-generate it? Or can I autogenerate a default?
You need to hand-edit your ~/.perl_developer.yml for setting-up your
pause permissions and so on. Presently, the upload only supports an
scp+http scheme.
>Will it work on any distribution, even ones I didn't create with
> CPDK? Or is there something specific about the way CPDK lays out
> files that I need to know about? (E.g. Changes have version + date
> on line 3).
The expectations might be somewhat specific in places, but you can
certainly turn off the actions or replace them with your own ./Build
actions. It's certainly designed to let you pick your own set of
sanity checks, but if your sanity differs from mine, you have to write
something to do the check.
It does work for M::B.
>Does it support git?
Not as written. I haven't gotten into the details of whether it would
be better to have a cpdk-specific adaptor or try to make VCfs handle
that.
>And -- FWIW, the requirements in Build.PL seem to be missing stuff.
Ah. You might need to look sideways in the svn for parts of this at the
moment.
> What the heck is VCfs?
An svn/svk agnostic object. This might have been surpassed by something
on the CPAN in the last couple years.
Thanks,
Eric
--
To a database person, every nail looks like a thumb.
--Jamie Zawinski
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
