On Wed, Apr 20, 2011 at 10:49 AM, Antonio Terceiro
wrote:
> This problem will happen with any upstream packages that do not build
> correctly, and is not specific to Ruby of gem2deb. In such cases, we
> must help upstream to fix their build system, and not add workarounds to
> our tools.
This is
Bryan McLellan escreveu isso aí:
> On Tue, Apr 19, 2011 at 9:22 PM, Antonio Terceiro
> wrote:
> > This other patch fixes the problem in a even better (an unintrusive)
> > way.
>
> Is this a problem that is unique to ruby-yajl, or one that may come up
> for other packages?
This problem will happe
On Tue, Apr 19, 2011 at 9:22 PM, Antonio Terceiro
wrote:
> This other patch fixes the problem in a even better (an unintrusive)
> way.
Is this a problem that is unique to ruby-yajl, or one that may come up
for other packages?
It's possible we can get upstream to rename the extension, but I
wonde
I hacked a config file in to specify an override file for where to
place the extension. I'm not sure if there are any other packages with
this issue or not, so it is hard to gauge the appropriate fix. With
this change to gem2deb, adding a debian/extension_path.overrides file
that contains 'yajl' pr
4 matches
Mail list logo
