From: "NARUSE, Yui" Date: 2010-09-10T10:08:37+09:00 Subject: [ruby-core:32270] Re: Can we convert the standard library to gems? 2010/9/9 Yusuke ENDOH : > 2010/9/9 Ryan Davis : >>> �3) advantage for the core team: they not have to do security >>> � � release if stdlib has a security issue, because "gem update" >>> � � can be used. >> >> I think FreeBSD + ports is a good model here. I see it as >> >> � �ruby + core libs : ruby stdlib :: freebsd distro : freebsd ports >> >> When a security announcement is released for freebsd itself, they usually >> provide a workaround + patch that you can apply immediately and then you >> can follow up with an official update. When a security announcement is >> released for a port, you can update the ports tree and update that port >> independent of a freebsd release. > > Interesting. �The two announcements for freebsd itself and a port > are released at once, right? �Otherwise it leads to zero-day > attack. > > The release manager must release not only full release but also and > push new gems, at once. �This is "Cons 1" I said. Separation of FreeBSD ports and pkgsrc is from the dependency to external libraries. http://www.freebsd.org/cgi/cvsweb.cgi/ports/lang/ruby18/ http://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/lang/ruby18/README.html -- NARUSE, Yui naruse@airemix.jp