On 15/05/10 at 09:45 -0300, Antonio Terceiro wrote:
I tried, but when I reached the point of trying it in the browser, I
ended up noticing that there was a hidden dependency of
librestclient-ruby1.8 on libopenssl-ruby1.8. On Squeeze,
libopenssl-ruby1.8 is included in libruby1.8, but on Lenny
Lucas Nussbaum escreveu isso aí:
On 15/05/10 at 09:45 -0300, Antonio Terceiro wrote:
I tried, but when I reached the point of trying it in the browser, I
ended up noticing that there was a hidden dependency of
librestclient-ruby1.8 on libopenssl-ruby1.8. On Squeeze,
libopenssl-ruby1.8 is
Tobi escreveu isso aí:
.. and another small patch, setting the html encoding to utf-8, because
the gem info might contain utf-8 characters. See e.g. nokogiri.
Tobias
Applied, thanks. :)
--
Antonio Terceiro terce...@softwarelivre.org
http://softwarelivre.org/terceiro
signature.asc
... and another small patch, setting the html encoding to utf-8, because
the gem info might contain utf-8 characters. See e.g. nokogiri.
Tobias
From 049447d5b844e91e997939f134271ce223d7146e Mon Sep 17 00:00:00 2001
From: etobi g...@e-tobi.net
Date: Mon, 10 May 2010 08:18:14 +0200
Subject: [PATCH
Antonio Terceiro wrote:
In the meantime, the current version is running on
http://gemwatch.heroku.com/
Thanks a lot!
I just noticed, that the timestamps of the files in the tarball are set to
1970-01-01, which would cause lintian errors if such tarball is used as
upstream source.
Antonio Terceiro escreveu isso aí:
Lucas Nussbaum escreveu isso aí:
On 22/04/10 at 11:14 -0300, Antonio Terceiro wrote:
Lucas Nussbaum escreveu isso aí:
- write a set of scripts to package from gems, including:
+ gem2tgz - convert gem to tgz, saving the gem metadata somewhere
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 23, 2010, at 2:10 AM, Lucas Nussbaum wrote:
No, we can't install packages ourselves (that are not in the
build-depends) during the build.
Is the point actually that we can't /uninstall/ Build-Depends during
the build?
- --
Opscode,
On 23/04/10 at 08:16 -0600, Joshua Timberman wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 23, 2010, at 2:10 AM, Lucas Nussbaum wrote:
No, we can't install packages ourselves (that are not in the
build-depends) during the build.
Is the point actually that we can't
On 22/04/10 at 00:11 +0200, Tobi wrote:
Lucas Nussbaum wrote:
3) Instead of providing several libfoo-ruby1.{8,9.1} packages, we
provide only one when it is possible (pure ruby packages), named
libfoo-ruby.
When this is not possible (case of packages that contain native extensions),
we
Lucas Nussbaum escreveu isso aí:
1) We base our packaging on rubygems. This doesn't mean that we package gems
directly. But we take upstream gems, convert them to .orig.tar.gz (easy), and
then apply our Debian-specific tools. That allows use to keep the
maximum flexibility of what we can do
On 22/04/10 at 19:40 +0900, NARUSE, Yui wrote:
0) We try to provide as much support as possible for all ruby interpreters
(well, at least 1.8 and 1.9.1, but maybe also jruby). However, we decide
on a default version (1.8 currently) that all libraries must support.
We'll release Ruby
On 22/04/10 at 07:33 -0600, Marcelo E. Magallon wrote:
When I was exploring a similar idea, I was thinking of going
with:
DIR=`basename $gem .gem`
mkdir $DIR
tar xOf $gem data.tar.gz | tar -C $DIR -xzf -
My own implementation:
#!/bin/bash
set -x
set -e
GEM=$1
BASENAME=$(basename $GEM
(2010/04/22 22:32), Lucas Nussbaum wrote:
On 22/04/10 at 19:40 +0900, NARUSE, Yui wrote:
0) We try to provide as much support as possible for all ruby interpreters
(well, at least 1.8 and 1.9.1, but maybe also jruby). However, we decide
on a default version (1.8 currently) that all
On 22/04/10 at 23:00 +0900, NARUSE, Yui wrote:
(2010/04/22 22:32), Lucas Nussbaum wrote:
On 22/04/10 at 19:40 +0900, NARUSE, Yui wrote:
0) We try to provide as much support as possible for all ruby interpreters
(well, at least 1.8 and 1.9.1, but maybe also jruby). However, we
decide
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello!
On Apr 21, 2010, at 2:07 PM, Lucas Nussbaum wrote:
0) We try to provide as much support as possible for all ruby
interpreters
(well, at least 1.8 and 1.9.1, but maybe also jruby). However, we
decide
on a default version (1.8
On 22/04/10 at 08:56 -0600, Joshua Timberman wrote:
Can we also please have RubyGems on Debian install in
/usr/local/lib/site_ruby, with binaries in /usr/local/bin? The
installation location of the current RubyGems is considered messy
and unexpected, and binaries are not in the default $PATH.
-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
Hi Marcelo,
Sorry to delay.
So currently repack.sh is getting call with debian/watch file
(uscan --force-download --rename --destdir ../tarballs).
It was a fix for subversion when you download upstream source and keep
it in ../tarballs before running svn-buildpackage.
I haven't said that
18 matches
Mail list logo
