-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Apr 22, 2010, at 9:25 AM, Lucas Nussbaum wrote:
This has been discussed at length in #448639 (/usr/local/lib vs
/var/lib) and #403407 (executables not in $PATH).
I'm not sure if these bug threads are conclusive, it seems that /usr/
local/lib and /usr/local/bin is preferred to /var/lib, yet the latter
is what the RubyGems package does.
Using Rake is usually a bit painful, because the Rakefile itself often
requires adding dependencies (like rubygems). It's better to keep
rubygems out of build dependencies since it allows to detect when the
scripts try to use it.
It can be, yes. But then the package maintainer has to track down how
the unit/spec tests are run and manually set up some other kind of
scaffolding to actually execute the tests.
I can see the point about keeping rubygems out of the build
dependencies, but if we're building packages in a sandboxed
environment such as with sbuild, can we not install rubygems, run the
tests and then uninstall rubygems?
The rule should probably be something like: "maintainers should make a
reasonable effort to run the test suite, provided it's not required to
install a myriad of dependencies and set up a complex test
environment.
That is fair!
Thanks,
- --
Opscode, Inc
Joshua Timberman, Senior Solutions Engineer
C: 720.334.RUBY E: [email protected]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)
iEYEARECAAYFAkvQiDoACgkQO97WSdVpzT1bHACfVEl652kRooEYu28v4rFxkoXx
JEsAnRjW+HgHeysG80TDW5HIsTrrNvUi
=6k4m
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive:
http://lists.debian.org/[email protected]
