On 08/19/2011 03:12 PM, Sören Eberhardt-Biermann wrote:
> Hi,
> 
> I just downloaded the Text_Diff Package from Horde. The package has
> quite large dependencies in the Horde framework.
> In eXtplorer I'm using different PEAR packages, with various
> dependencies - so switching to Horde_Text_Diff would blow up eXtplorer
> even more (+172kb). I must always think of having to disribute the
> package outside of the Debian world. And there it's the best to have a
> small package (<2MB).
> 
> But besides that I'm sure that changing the code to use Horde_Text_Diff
> wouldn't be difficult...
> 
> Sören

Hi Soren,

Thanks for your insight and quick reply, it's really appreciated to have
a reactive upstream author, and your prompt reply over the last months
is pushing me to trust you even more.

1/ Few remarks about embedding libraries

What I think would be great would be that, inside your (upstream)
packaging, would be if you separated the libraries you are using more
clearly. Because currently, it might be possible for us, doing the
Debian packaging, to miss some embedded things. This just happened with
php-text-diff when Roland wanted to package a more recent version, it
might happen again. Ideally, you'd have a "3rdparty-library" folder that
we would just delete for the use in Debian. That's just a suggestion
though, but that would really help us. If you can't do that, then having
a text file listing the embedded files would be ok too. That way we
could write a script like this:

embedded_files=`cat embedded_files`
for i in $embedded_files ; do rm -r $i ; done

instead of having to maintain a script to do it. Anyway, Roland, when
you are packaging a software, I would suggest you to systematically
check the upstream files, since even upstream can sometimes forget some
things he embedded (it happened once with eXtplorer too).

2/ php-text-diff / horde-text-diff

For php-text-diff, I don't see much other possibility than using the new
one from Horde if it is the only one that is maintained. Even for your
embedded version inside the released eXtplorer, using a PEAR package
that isn't maintained is dangerous, if an issue raises.

By the way, there is currently an ongoing effort to package all the PEAR
modules of Horde (in fact, there's an ongoing effort to package horde
itself), which is why the "pkg-php-tools" was created. I think it'd be
worth to ask in [email protected] what is the status
of the package.

Cheers,

Thomas



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to