Re: debian's dependancies
I would suggest to discuss the issue on debian-devel
On Wed, 26 Jan 2000, Tim Janik wrote:
> hy christoph,
>
> i've been using debian for quite some time now, and
> the dependacy system surely has its advantages.
> however for a developer it also has some major
> shortcomings, as soon as your project becomes a
> dependancy for other packages being installed.
> for instance i build several core components of
> GNOME from CVS and also co-maintain gtk and glib.
> since i need to frequently reinstall all these kinds
> of packages, i can't actually use the libglib1.2,
> libgtk1.2, etc... libraries shipped with debian
> potato proper. yet i do always have working versions
> of all of them installed on my system. now i'd still
> like to user several third party applications that
> depend on these libraries, but that is not possible
> because dpkg doesn't know i've got the libraries installed.
>
> rather than doing ugly hacks like installing libglib1.2,
> then manually removing all the files in /usr/lib/* and
> other places, just to make dpkg *think* those libraries
> are installed, couldn't we *simply* have one file
> /etc/dpkg/assume-installed, where i'd put:
>
> libglib1.2
> libglib1.2-dev
> libglib1.2-dbg
> libgtk1.2
> libgtk1.2-dev
> libgtk1.2-dbg
> liborbit20
>
> etc...
>
> that apt and dpkg would parse and *always* assume the newest
> version of these packages is installed?
>
> i picked your email adress because it apperas in lots of the
> package building manuals etc..., if there's actually some other
> person better suited to answer this request, please be so kind
> as to point me at him.
>
> ---
> ciaoTJ
>
>
Reply to: