--- On Fri, 9/12/11, Theppitak <t...@linux.thai.net> wrote:
> This case is common. Just set PKG_CONFIG_PATH and
> LD_LIBRARY_PATH
> environments to your home-based dir.
That does not do. How many piece of demo/still-in-dev software I (or somebody
else) want to *try*, which needs those?
> > libdatrie does not seem to have libthai dependency
> currently?
>
> No.
I think you could think about how many dependent software libdatrie has, and
whether it make sense to bundle it in the swath release source tarball. (you
can keep the development separate).
R does that whenever it goes into release (it bundles a few 3rd party general
libraries like libjpeg and pcre, as well as some R-specific ones which have
separate dev repositories).
> I also considered this, but libdatrie has had its own uses
> in many
> applications. Not just for non-Thai dictionaries,
> it's known to have
> been used in information retrieval projects, or even
> bio-informatics.
> Benefit of splitting it outweighs the cost of bundling it
> in every
> piece of such software. And in your particular case
> of casual tryout,
> common technique is well-known.
I doubt that. libdatrie is not known at all from any of redhat/fedora's 3rd
party repositories. In fact it was difficult to find by googling.
> Yep, I agree it's very complicated, compared to this:
>
> Suppose you want to install locally under
> ${HOME}/local. Then, in your
> ~/.bashrc:
>
> export PKG_CONFIG_PATH=${HOME}/local/lib/pkgconfig
> export LD_LIBRARY_PATH=${HOME}/local/lib
> export PATH=${HOME}/local/bin:${PATH}
How far you do before you start to have a shadow / under your home? That's for
one small command-line utility swath.
> Not satisfied after trying? "make uninstall" is
> available to help.
That depends on two things:
- the original partly used src/ is still available . That shall not be the case
if say, I am trying it out briefly, (meanwhile, I might want to tidy up), then
a few months later decided it is not for me.
- if it is to clear-up after a messed-up TEXMF or /usr/local, the last thing
one wants is to run another automated script to hope to clean up a mess.
> No, I didn't, as demonstrated above. I think the
> technique is very
> common.
common, where?
> As I said, the home installation technique is very
> common. It would
> have made it too tedious to read to list all well-known use
> cases in
> the first place.
I see why it doesn't get into TeXLive...
You are not making it easy for *potential* user to try it out without
installing, and that's just a tiny command-line tool.
_______________________________________________
Cjk maillist - Cjk@ffii.org
https://lists.ffii.org/mailman/listinfo/cjk
