Tatsuhiko Miyagawa's blog

Tatsuhiko Miyagawa's Podcast: ep11: Google I/O 2013 (kenn, mootoh)

Fri, 17 May 2013 14:36:07 -0700

Tatsuhiko Miyagawa's Podcast: ep11: Google I/O 2013 (kenn, mootoh):

収録時間 46:22 | Download MP3 (26MB)

Kenn Ejima さん (@kenn), Motohiro Takayama さん (@mootoh) を迎えて、Google I/O, Google Glass, Google Play Game Services などについて話しました。

番組へのフィードバックは Twitter にて @miyagawa またはハッシュタグ #bulknews にてお寄せください。

Show Notes

Google IO

The best of Google I/O 2013…

2週間で3エピソードとちょっと飛ばし気味ですが、時事ネタということでGoogle I/O 話。翌日でキーノートちょっと忘れてますが、参加してたmootohさんのおかげでいろいろ拾えましたね。後半の Game Services 話は業界トークっぽくて面白かったです。

録音しながらライブストリーミングもしてみたんですが、時間帯の関係もあってフィードバックをもらうのが難しかったですね。twitter 以外にも Lingr とかのほうがエンゲージしやすいのかな。いろいろ試行錯誤してみる必要ありですね。

Podcast recording and editing

Fri, 17 May 2013 11:07:00 -0700

Here’s what it looks like when it comes to editing my (semi-badly recorded) Podcast episodes.

When I first heard 5by5/Mule’s podcasts, i was really impressed by the audio quality of their shows, since like many of you, i had a feeling that “Podcast is by amateurs and audio is mediocre at best”. I was blown away.

So I did a little bit of research before starting my show, because I want to make it sound good too. Jason Snell’s article on MacWorld explains the current method of my recording.

Skype, Everyone Records, GarageBand

The tl;dr for that is, I use Skype Call Recorder to record both my audio and guest(s) on Skype, on separate tracks. It’s great that it records my audio locally, not via Skype, so it’s a direct input from my Mic.

I ask guests to record their local audio using QuickTime too and send files after recording. Then I synchronize them with Skype’s recorded audio, then discard the Skype audio file.

Now I get everyone’s locally recorded audio, on separate tracks on GarageBand, and I only need to edit when there’re murmuring or conflicts, etc. In Theory.

I’m often asked how long it takes to edit the show - if the show is one hour, it usually takes 2 to 3 hours.

Microphone and Headphones

Recent episodes needed a little bit more of my editing work than previously - this is not to particularly blame anyone but the technologies/hardware, because it’s a mere audio leak on other’s ends.

Basically when I speak, my voice leaks on the guest’s track because their mic picks up the audio from the earpiece, and makes an echo/delay sound effect that I need to cancel out. That leads to the chaotic GarageBand editing shown earlier. Noise gate works to cancel that, but it also cancels the valid voice and i avoid doing it.

I ask everyone to use headphone/earphone, but sometimes the microphone is too close to them, or the headphone is not solid enough and leak audio from there. It doesn’t seem to happen to everyone (which is good), so it should definitely be related to the combination/setup of the microphone and headphones.

My particular setup is Blue Yeti USB Microphone and Klipsch IMAGE S4 and don’t have that problem on my end. Klipsch has a very crisp sound with very little sound leak, as an in-ear headphone.

In terms of not leaking audio, Over-the-ear Headphones should be the best, but unless you have a microphone with monitoring capabilities (like Yeti :D), it might be difficult to hear what you speak while speaking.

I guess this is one of the difficulties of doing the show with irregular guests, since we can’t ask guests to invest some money on microphones/headphones, which I would if I do recurring/fixed guests :)

Tips

Here’s a simple thing: don’t use Apple’s iPhone headset. Its audio isn’t bad, but it picks up a lot from its earpiece, and makes a big noise when touched with your clothes. Speaking of Apple, Macbook Pro Retina’s dual USB microphone is fantastic, assuming you don’t have a a big ambient noise.

Also, some of the Japanese podcast shows I listen to have severe audio quality issues (although I’m not sure if they read this in English ;p) - Just don’t record the show in a cafe/restaurant with big ambient noise. Also, double your bitrate and make a mono MP3, rather than low bitrate stereo files.

—

Anyway this was my current setup. For the latest episode 11 where we talked about Google I/O, we also experimented with the live streaming with Mixlr. I will explain the setup about it (pretty simple if you have a spare Mac mini) later if you’re interested :)

Tatsuhiko Miyagawa's Podcast: ep10: RailsConf, Ruby 2.0, Rails 4 (mrkn, r7kamura)

Sun, 12 May 2013 19:28:00 -0700

Tatsuhiko Miyagawa's Podcast: ep10: RailsConf, Ruby 2.0, Rails 4 (mrkn, r7kamura):

bulknews-podcast:

Kenta Murataさん (@mrkn), Ryo Nakamuraさん (@r7kamura) を迎えて、RailsConf, Ruby 2.0, Rails 4, Chanko 2.0, RubyKaigi, YAPC などについて話しました。

今週は日本語営業に戻って、mrkn, r7akamura とRuby 話をしました。ちなみに３人の収録だと間が持ちやすくていいんですが、編集がちょっと大変。

Rails 2.3 is Kansas

DHH の Kansas ネタはConfreaksにKeynoteが上がってました。13分あたり。hkmurakami さんが詳しく解説してくれてます。日本の2ch でよくでる群馬県ネタに近いものがありますね。

Tatsuhiko Miyagawa's Podcast

Wed, 08 May 2013 00:37:02 -0700

Tatsuhiko Miyagawa's Podcast:

bulknews-podcast:

On the episode 9 of my podcast, featuring Jesse Vincent (@obra), we discussed his recent experiments to build his own keyboard.

Some of my followers on Twitter and friends on Facebook asked if there was any plan for an English episode of my podcast.

So here it is, with Jesse Vincent, we talked about his recent exploration of making his own Keyboard. We also discussed little bit about perl, and OSDC.TW, the conference we just attended a couple of weeks ago.

Might want to do more of English episodes in the future, but comments and feedback is always appreciated.

Starman 0.3011

Wed, 24 Apr 2013 18:15:27 -0700

Starman 0.3011:

Disabled flock serialization when it’s unnecessary. This will improve the performance when you have many Starman worker processes on Linux systems (kazeburo) #69

It’s a minor version update, but contains very important fix - it bypasses flock serialization in accept in most UNIX systems where there’s only one port being listened. It will boost the performance when you have a bunch of worker processes. Thanks to kazeburo for the patch on his blog!

Freeze CPAN deps with PAUSE git

Wed, 24 Apr 2013 13:21:00 -0700

Freeze CPAN deps with PAUSE git:

PAUSE is the backend of CPAN module upload server, and since April 2012, thanks to rjbs, for every perl module upload, it commits the index list (as well as author/permission mapping). And now it is available on github. Thanks Andreas!

This makes it so easy to freeze CPAN module dependencies for your application solely based on time.

First, check out the repo, and then specify the revision with date time you want to freeze at:

git clone git://github.com/batchpause/PAUSE-git.git
cd PAUSE-git
git checkout `git rev-list -n 1 --before "2013-01-01 00:00" master`

Then, refernce that 02packages from cpanm:

cpanm --installdeps . \
  --mirror-index /path/to/PAUSE-git/02packages.details.txt
  --mirror http://backpan.perl.org/

That’s it, really.

If you want more control over versions, dev releases and git forks, you might need Carton. And you can only go back to 2012 April and no older than that. But for a simple time-based index, this is all you need.

kazeburo/Monoceros · GitHub

Wed, 24 Apr 2013 12:57:01 -0700

kazeburo/Monoceros · GitHub:

Monoceros is PSGI/Plack server supports HTTP/1.0. Monoceros has a event-driven connection manager and preforking workers. Monoceros can keep large amount of connection at minimal processes

Great addition to the PSGI/Plack web servers. Gets the best of event-based servers to handle C10K connections while working a pool of preforking workers.

nginx 1.4.0 is out

Wed, 24 Apr 2013 12:54:00 -0700

nginx 1.4.0 is out:

nginx-1.4.0 stable version has been released, incorporating many new features developed in the 1.3.x branch - support for proxying of WebSocket connections, OCSP stapling, SPDY module, gunzip filter and more.

Listen-IT: ３編セット４０％オフキャンペーン中

Wed, 17 Apr 2013 15:00:00 -0700

Listen-IT: ３編セット４０％オフキャンペーン中:

宮川達彦さんのPodcastをスポンサーしましたので、その記念に４０％オフキャンペーン開催中です。母音編、子音編、文章編、３つセットでご購入いただくと定価２０００円なのですが、今なら１２００円。全部で６０レッスン、６６９単語と１７０の文章が詰まっていますので、１レッスン２０円、単語／文章当たり１．４円と大変お買い得です！

Great app, 40% off sale. Go buy it and support my podcast :)

Tatsuhiko Miyagawa's Podcast: Podcast ep8: ゲスト伊藤直也高林哲

Tue, 16 Apr 2013 21:37:41 -0700

Tatsuhiko Miyagawa's Podcast: Podcast ep8: ゲスト伊藤直也高林哲:

bulknews-podcast:

スポンサー: Listen-IT

伊藤直也さん (@naoya_ito) 高林哲さん (bkノート) をゲストに迎えて、日米キャリアパス、スクリーンキャスト、ペアプログラミング、エンジニアリング英語などについて話しました。

おなじみのお２人と、都内某所で収録しました。後ろで将棋を指してる音が聞こえます :)

本記事にもありますが、収録機材がノイズを結構拾ってしまっていて、ちょっと気になるかもしれませんがご了承を。やっぱりマイクのクオリティが音質に直結しますね。Skypeだとあとで編集はいろいろできるんですが、直録りはいろいろ難しいです。

このあとまだまだたくさんしゃべったんですが、長くなったのでここまで。またお蔵出しもあるかもです。

Tatsuhiko Miyagawa's Podcast: ep7 ゲスト: ゆーすけべー (yusukebe)

Wed, 03 Apr 2013 01:11:18 -0700

Tatsuhiko Miyagawa's Podcast: ep7 ゲスト: ゆーすけべー (yusukebe):

bulknews-podcast:

収録時間 40:06 | Download MP3 (24MB)

第７回は和田裕介さん (@yusukebe) をゲストに迎えて、Perl プログラミング、フレームワーク、モジュール開発、YAPC などについて話しました。

いつになく、Perl成分の濃い話になりました。最近、昔話多め感もありますが、それもアリということで。

後半の方ででてきた、Fat vs Thin libraries の話は、前回のYAPC::Asia のパネルディスカッションでも同じような話をしたんですが、YAPCでのスピーカー勢の（大半の）考え方と、実際に使われているモジュール・ライブラリ間でギャップがあったりしないかなぁ、という思いを最近持っていて、ネタにしてみました。

軽いものが使いやすいのはそうなんですが、重いもの、依存が多いものにはそれなりの理由があったり、枯れていたりというメリットもあるわけで、適材適所かなぁ、と最近は思っています。ま、同じ事ができて速いなら、そっちのほうがいいには決まってるんですけどね。

test_requires all the way

Fri, 29 Mar 2013 23:17:00 -0700

tl;dr Today possibly for the first time ever, CPAN toolchain ecosystem all support test requirements as separate from build requirements. I can’t be happier ever.

Little bit of history. Timeline might be not in the correct order.

Module::Install always had test_requires() with forward compatibility in mind. However META spec v1.4 didn’t support specifying test requirements separate from build requirements. So the most tools merge them as a build requirement, including Module::Install itself. This means most of the Test:: module dependencies, even though they are only used for testing, were installed even when notest options is supplied (with CPAN.pm and cpanminus).

META spec v2.0 came out, and it allows META (and MYMETA) to specify test requirements separately.

cpanm supported parsing test requirements separately, and skips installing test prereqs when —notest is in use. But at that time, most of the tools did not support emitting test requires apart from build requires.

Except Module::Build::Tiny, which just copies META.json to MYMETA.json upon installation, so if you use an authoring tool such as Dist::Zilla or Milla to emit META.json with test requirements apart, it will be skipped.

Meanwhile rjbs added TEST_REQUIRES support to MakeMaker at Paris QA hackathon 2012. 7 months later MakeMaker 6.63_03 was released with the fix, and non-dev version was just out in December.

Same fix was added to Module::Build by tokuhirom and released as 0.40004 today.

Now, what should happen is to update Makefile.PL and Build.PL to make use of these new features - I patched Dist::Zilla so that MakeMaker and ModuleBuild emitters will use test_requires when the installer has the version with the support for it.

I’m trying to fix Module::Install similarly, but as of this writing I’m not that hopeful - if someone wants to take over my work to make it merged that’d be super. But at this point I’d rather give up and stop using Module::Install.

Anyway, now when you have a module that is only used for testing, it will be (and has to be) declared and emitted correctly as a test dependency, and when you run CPAN installers, at least cpanm, with “no test” option, they won’t be installed. This is a very important milestone.

Milla, a Dist::Zilla profile that doesn't suck (screencast)

Wed, 27 Mar 2013 18:53:00 -0700

Ok, that was a little link bait title.

I’ve been a big fan of Module::Install - it automatically figures out the metadata of my module with just all_from, and does the right thing creating META files. Then it bundles itself in inc/ so that if you install from CPAN you don’t need to have Module::Install pre-installed.

But not everybody likes it, especially contributors who need to install plugins before doing anything, or users who want to grab the latest from git.

The problem is, Module::Install is just a wrapper for MakeMaker, and MakeMaker and Module::Build are not the right tool to create a distribution.

Dist::Zilla is a pioneer in this field, to provide the complete authoring environment for the CPAN distribution, while having the ability to export MakeMaker/Module::Build compatible build files, so that end users don’t need to have that upon installation.

However Dist::Zilla kind of sucks. Well, that was a strong word - it has been coded and maintained actively, so it’s great. But its user experience could have a little improvements.

Milla is my first attempt to address that issue. It is a set of profile - PluginBundle, MintingProfile and command line wrapper, so that you can use it with almost zero-configuration and should do the right thing.

There’s some limitation and assumption that do not work for everybody, but at least for me I hope to replace 95% of my CPAN modules with Milla in the coming weeks.

Here’s a screencast to show you how to use it.

If you already have modules written with MakeMaker/Module::Install + ShipIt, see the Migration document for the details. I might make a new screencast just for the migration.

Hope you enjoy Milla. If you dislike the 195 dependencies it needs, check out our sister project Minilla as well.

Tatsuhiko Miyagawa's Podcast: ep6 ゲスト: Naoya Ito

Wed, 20 Mar 2013 23:01:00 -0700

Tatsuhiko Miyagawa's Podcast: ep6 ゲスト: Naoya Ito:

bulknews-podcast:

収録時間 41:20 | Download MP3 (23.5MB)

第６回は伊藤直也さん (@naoya_ito) をゲストに迎えて、Kindle 出版、GitHub、Google Reader などについて話しました。

第１回に続き、naoyaさんに出てもらいました。

「非公式なAPI」

後半で出てくる Google Reader APIの話で、「野良API」って言葉を使ってますが、紛らわしい表現だったかもなので、ちょっと補足。

「野良API」というと第三者が無断でつくったAPI、のようにも聞こえますが、そうではなく、「非公式なプライベートAPI」という方が正しい。

ここでいう非公式なAPI、というのは、Google Reader のウェブサイトが Ajax で使っているエンドポイントや、Google公式の Reader アプリが使っているプライベートAPIをリバースエンジニアリングしたAPI、という意味で使っています。仕様についても Google は一度も公開したことはなく、有志がリバースエンジニアリングした仕様をGoogle Code上で公開してるもので、これを feedly などは使っていた、という話です。

ゲストの人選

naoyaさんが２回めということもあって、「もう２周目」？とかTwitter で意見をもらったりしてます。

もともと、ゲストを週替りにしてインタビューする、という発想ではなくて、その時話したい「ネタ」があって、それに最適な人をキャスティングする、という発想をベースにしていました。MessagePack のissueの話、Ruby 2.0 のリリースの話、その開発者に聞くのが一番いいですよね :)

とはいえ、ネタにとらわれずに「いいとも」あるいは「徹子の部屋」的に人にフォーカスした回もあってもいいかなと思っていますし、ep4の高林さんの回なんかはそういう感じですね。

その辺もいろいろバランスをとってやって行きたいと思いますが、まだまだいろいろ試行錯誤ですので、フィードバックもらえるとうれしいです！

Tatsuhiko Miyagawa's Podcast: Podcast ep5: 2013/03/13 ゲスト: まつもとゆきひろ (matz)

Tue, 12 Mar 2013 19:38:31 -0700

Tatsuhiko Miyagawa's Podcast: Podcast ep5: 2013/03/13 ゲスト: まつもとゆきひろ (matz):

bulknews-podcast:

収録時間 35:12 | Download MP3 (21MB)

第５回はまつもとゆきひろさん (@yukihiro_matz) をゲストに迎えて、Ruby 2.0 などについて話しました。

番組へのフィードバックは Twitter にて @miyagawa またはハッシュタグ #bulknews にてお寄せください。

Perl versions usage stats (with cpanm)

Tue, 12 Mar 2013 16:34:00 -0700

A week ago I added a neat little feature in cpanm 1.6004 to report its perl versions in User-Agent strings (regardless of whether it uses LWP, curl, wget or HTTP::Tiny) in addition to cpanm’s own version.

One week later, there seems more than 60% of the users seem to have upgraded (including people who runs curl -L cpanmin.us which always run the latest stable), and we get a pretty interesting number.

(In case you’re wondering: the big ones are 5.8.8, 5.10.1, 5.14.2 and 5.16.2. Graph on the link uses google chart API which allows you to hover over the graph to see which portion represents which perl version)

Perl versions used with cpanm is a graph calculated out of 10K recent requests in CPAN Meta DB uniqued by the IP address, updated daily on 1am UTC.

The graph can be viewed using ?date=YYYYMMDD permanent link as well.

Few notes: This does not reflect (yet) the users who use older versions of cpanm, which may or may not be the installation which tend to use older versions of perl. It also doesn’t include cpanm users who uses --mirror-only to work with local CPAN mirrors without hitting CPAN Meta DB nor MetaCPAN. I believe these numbers can be either a) so small that it’s ignorable or b) significant, but spread across many versions in the same way those who don’t.

The number might look low for the recent 10K requests. There are several reasons, but the biggest one is that many requests will end up with pulling 10+ CPAN dependencies, which are (correctly) deduplicated into one.

It’s just one metric, and I don’t argue that it’s accurate, but I believe it’s not that far away, and would be interesting to see how it settles over time.

What is cpanfile and why do I want to use it

Sat, 09 Mar 2013 12:35:00 -0800

So there seems to be a couple of blog posts and even conference talks about cpanfile. It’s great, but just to make sure everyone gets what it is and why they want to (or don’t want to) use it for their stuff, here’s some clarification from the author.

tl;dr for japanese - this slide deck at Hokkaido.pm has a great intro for what cpanfile is.

cpanfile is made specifically to address the two following use cases, while the second one is kinda accidental.

1) “I have an app (web app, command line script) and want to manage its CPAN module dependencies somehow. I created a fake Makefile.PL to describe them, even though I don’t have a plan to release it to CPAN.”

2) “I have a Perl module on my git repository and want my contributors to be able to install from the repo, but they keep saying they can’t load inc/Module/Install.pm, and I don’t want to bump META.yml every time or include inc/ in the repo.

cpanfile is a Module::Install-like DSL to describe CPAN module dependencies. It comes with a module to parse out that file, but isn’t tied to any specific builder nor installers.

It is useful for Perl application developers who want to describe CPAN dependencies, and being able to install them with carton install or cpanm --installdeps .

For CPAN module authors, cpanfile is not something you really need to switch to, although you will (soon) have a benefit of easier installation from git repository if you have one. The reason i wrote “soon” is that cpanm 1.6 as of this writing doesn’t have the ability to bootstrap modules with M::I from git repo - it’s a known issue and I am trying to address that in the sane way before cpanm 1.7. (There’s a workaround out there to specify Module::Install in configure_requires but that is wrong because that’s not necessary once shipped to CPAN)

Standard CPAN installers (CPAN.pm, CPANPLUS, cpanm) work with META files (and then MYMETA after configuration) to detect dependencies. It’s a standard, and cpanfile doesn’t intend to replace them or anything at all. If you decide to use cpanfile to describe deps for your CPAN modules however, you should use Module::Install::CPANfile or Module::Build::Pluggable::CPANfile so that it will transparently work with MYMETA protocol.

FAQ

I am a CPAN author and keep META.yml in the repo. Should I switch to cpanfile?

If your configuration is static and you have no problem remembering to bump META.yml in the repo, that’s just fine. However, putting “Module::Install” (for example) into your configure_requires doesn’t sound right since it’s not necessary once it’s shipped to CPAN. Committing the whole inc/ is another way to go, but it feels like an unnecessary work to me.

I have a web app and want to use cpanfile to deploy to the cloud. Which provider supports cpanfile?

Most PaaS providers (dotcloud, heroku through buildpack, etc.) uses cpanm --installdeps . to install dependencies. Once they upgrade cpanm to 1.6 or later, it will automatically figure out the dependencies out of cpanfile. If they don’t have 1.6 yet, why not requesting them to upgrade it?

I use dzil for my CPAN modules and am not sure what you are talking about.

Great, Forget about this post.

However, contributors to your module may have hard time installing dzil first and then remembering what command to run to test/install because it’s different from other CPAN module convention. cpanfile may be able to help that, but i’m still trying to figure out.

So which phase should I put Module::Install into in cpanfile?

It should most likely be develop, and cpanm will detect the “development environment” i.e not from CPAN tarball, but that’s still being ironed out.

Tatsuhiko Miyagawa's Podcast: Podcast ep4: 2013/03/06 ゲスト: 高林哲

Tue, 05 Mar 2013 15:47:44 -0800

Tatsuhiko Miyagawa's Podcast: Podcast ep4: 2013/03/06 ゲスト: 高林哲:

bulknews-podcast:

収録時間 31:04 | Download MP3 (17MB)

第４回は高林哲さん (Google+) をゲストに迎えて、バッドノウハウ、ソフトウェアエンジニアリング、コードレビューなどについて話しました。

番組へのフィードバックは Twitter にて @miyagawa またはハッシュタグ #bulknews にてお寄せください。

stop shipping MYMETA to CPAN

Thu, 28 Feb 2013 15:48:20 -0800

You’re a new CPAN author (congratulations!) or you have an old distribution that is about to be updated for the first time in years, and you find MYMETA.yml and MYMETA.json in your working directory that git or shipit warns about. You think: What are these files? Should I package these files?

tl;dr - add MYMETA.yml and MYMETA.json to .gitignore and MANIFEST.SKIP (if you have one), and do not include them in the tarball.

MYMETA.yml/json files are a relatively new approach for CPAN installers (CPAN, CPANPLUS, cpanm) and module build tools (MakeMaker, Module::Build) to communicate the configured dependencies on the end-user’s system.

MYMETA is just like META files in terms of the file format and data structure, but whereas META.yml is generated by the distribution author (you), MYMETA.yml is generated by the end user at a configuration time.

Including MYMETA files in MANIFEST and a distribution tarball does not make any sense, and could cause potential problems confusing CPAN installers - do not make them part of your distribution.

(Why this post? Many CPAN authors have been confused or unaware what MYMETA files are and simply include them in the distribution)

Podcast ep3: 2013/02/27 ゲスト: Sadayuki Furuhashi, Kiyoto

Wed, 27 Feb 2013 03:05:46 -0800

bulknews-podcast:

第３回は古橋貞之さん (@frsyuki)、kiyotoさん (@__kiyoto__) をゲストに迎えて MessagePack について話しました。

Subscribe via iTunes | RSS

Tatsuhiko Miyagawa's blog

Tatsuhiko Miyagawa's Podcast: ep11: Google I/O 2013 (kenn, mootoh)

Show Notes

Podcast recording and editing

Skype, Everyone Records, GarageBand

Microphone and Headphones

Tips

Tatsuhiko Miyagawa's Podcast: ep10: RailsConf, Ruby 2.0, Rails 4 (mrkn, r7kamura)

Rails 2.3 is Kansas

Tatsuhiko Miyagawa's Podcast

Starman 0.3011

Freeze CPAN deps with PAUSE git

kazeburo/Monoceros · GitHub

nginx 1.4.0 is out

Listen-IT: ３編セット４０％オフキャンペーン中

Tatsuhiko Miyagawa's Podcast: Podcast ep8: ゲスト 伊藤直也 高林哲

Tatsuhiko Miyagawa's Podcast: ep7 ゲスト: ゆーすけべー (yusukebe)

test_requires all the way

Milla, a Dist::Zilla profile that doesn't suck (screencast)

Tatsuhiko Miyagawa's Podcast: ep6 ゲスト: Naoya Ito

「非公式なAPI」

ゲストの人選

Tatsuhiko Miyagawa's Podcast: Podcast ep5: 2013/03/13 ゲスト: まつもとゆきひろ (matz)

Perl versions usage stats (with cpanm)

What is cpanfile and why do I want to use it

FAQ

I am a CPAN author and keep META.yml in the repo. Should I switch to cpanfile?

I have a web app and want to use cpanfile to deploy to the cloud. Which provider supports cpanfile?

I use dzil for my CPAN modules and am not sure what you are talking about.

So which phase should I put Module::Install into in cpanfile?

Tatsuhiko Miyagawa's Podcast: Podcast ep4: 2013/03/06 ゲスト: 高林哲

stop shipping MYMETA to CPAN

Podcast ep3: 2013/02/27 ゲスト: Sadayuki Furuhashi, Kiyoto

Tatsuhiko Miyagawa's Podcast: Podcast ep8: ゲスト伊藤直也高林哲