[DRE-maint] ruby-setup-rb.mk, and ftbses
lucas at lucas-nussbaum.net
Mon Jan 14 19:28:49 UTC 2008
On 14/01/08 at 11:53 -0600, Gunnar Wolf wrote:
> Lucas Nussbaum dijo [Sat, Jan 12, 2008 at 08:14:54PM +0100]:
> > > This is the point, the class links setup.rb if one is not already
> > > present in upstream source. So at clean time, it removes it only if it
> > > is a symlink. (This code extract is in the clean target.)
> > > BTW the fix is not mine.
> > This doesn't work. The idea is to always use setup.rb from the package.
> > Using upstream's setup.rb will make us use old versions of setup.rb,
> > which won't support some of the options we use.
> AIUI, this might end up not working - Setup.rb does _not_ claim to
> maintain backwards compatibility. From the documentation :
> Backward Compatibility
> I do not assure any backward compatibility for the setup.rb. If
> you'd like old behavior, just use old version.
> I think that, if upstream ships a setup.rb, we should just use
> it. libsetup-ruby should be useful in the (many) cases where we
> _don't_ have it.
But then, we have to determine the version of setup.rb the package is
shipping, and pass it the right options. Which is insane :-)
There's no perfect solution. But it sounds better to have *one* setup.rb
for all our packages. Then, we just have to carefully maintain it
(test-rebuild all our packages when we want to upgrade it).
| Lucas Nussbaum
| lucas at lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lucas at nussbaum.fr GPG: 1024D/023B3F4F |
More information about the Pkg-ruby-extras-maintainers