Your message dated Thu, 12 May 2011 08:09:45 -0700
with message-id <[email protected]>
and subject line Re: Bug#626463: Idea
has caused the Debian Bug report #626463,
regarding gem2deb: fails with same-named files
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
626463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626463
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gem2deb
Version: 0.2.2
Severity: normal
I am trying to install different flavors of markdown (rdiscount
and redcarpet). As a gem, this is possible, with gem2deb packages
it fails:
dpkg: Fehler beim Bearbeiten von ruby-rdiscount_1.6.8-1_amd64.deb
(--install):
Versuch, »/usr/lib/ruby/vendor_ruby/markdown.rb« zu
überschreiben, welches auch in Paket ruby-redcarpet 1.13.1-1 ist
Fehler traten auf beim Bearbeiten von:
ruby-rdiscount_1.6.8-1_amd64.deb
AFAIK the gem system keeps the files in separate subdirectories,
probably this would help to get the packages installable.
The true "Debian way" might be using the using the alternatives
system to determine what's meant by "require 'markdown'" in such
a situation.
Thanks for your effort!
Michael
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (900, 'testing'), (500, 'stable-updates'), (500,
'proposed-updates'), (500, 'stable'), (10, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.38-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages gem2deb depends on:
ii build-essential 11.5 Informational list of build-essent
ii debhelper 8.1.6 helper programs for debian/rules
ii devscripts 2.10.72 scripts to make the life of a Debi
ii perl 5.10.1-20 Larry Wall's Practical Extraction
ii ruby1.8 1.8.7.334-4 Interpreter of object-oriented scr
ii ruby1.8-dev 1.8.7.334-4 Header files for compiling extensi
ii ruby1.9.1 1.9.2.180-3 Interpreter of object-oriented scr
ii ruby1.9.1-dev 1.9.2.180-3 Header files for compiling extensi
ii rubygems [rubygems1.8] 1.7.2-1 package management framework for R
gem2deb recommends no packages.
gem2deb suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Michael Below escreveu isso aí:
> What about a solution like this:
>
> If a gem contains a toplevel file with a name different from the gem
> name, register it as an alternative.
What if the gem provides a file called 'erb.rb', should add alternatives
involving Ruby's standard library? :-)
That's not the right solution for this case. Different libraries are
supposed to NOT install random files under the $LOAD_PATH, specially NOT
files with the same name.
A lot of people have made this point publicly already:
http://weblog.rubyonrails.org/2009/9/1/gem-packaging-best-practices
http://yehudakatz.com/2009/07/24/rubygems-good-practice/
When using rubygems it "works", i.e. you can install the libraries. But
the effects of `require 'markdown'` are unpredictable: depending on
which gem gets loaded first, one or the other will be loaded. If they
don't provide _exactly_ the same API, then your code will break in
non-deterministic ways.
So, in principle not being able to install both libraries in a Debian
system is a bug in the libraries, not in gem2deb. If they are ever
packaged properly into Debian, their maintainers will probably have to
make one package conflict and/or replace each other.
--
Antonio Terceiro <[email protected]>
http://softwarelivre.org/terceiro
signature.asc
Description: Digital signature
--- End Message ---
