Em 08-01-2014 13:09, Armin K. escreveu:
> On 01/08/2014 02:56 PM, Igor Živković wrote:
>> On 2014-01-08 14:40, Fernando de Oliveira wrote:
>>>
>>> Another clarification would be in GLU, which does not have a
>>> introduction, and is included in the page, would deserve 
>>> clarifications,
>>> too, I think.
>>>
>>> Also, I have a doubt if it could have its own page. Reason is my recent
>>> experience with audacious, that I updated, where some dependencies are
>>> for the main package and others only for the plugins (and I still am
>>> thinking if would also deserve to be split in two pages, with the
>>> plugins being runtime required dependency for the main page). Included
>>> this in the discussion, because depending on the opinions, perhaps I
>>> should open a thread asking you all about this, sorry for the OT.
>>
>> I don't think GLU is used by anything in the X Window System Environment 
>> chapter. Same thing for makedepend. Those two packages should probably 
>> be moved.
>>

Have been studying makedepend all this morning. Before, I had just
installed it, without paying much attention, perhaps only to fix the
xorg chain, can't remember now. So, What I am writing in the following
about it might be wrong.

First, it seems that only one package depends on it, but only
optionally: JS-17.0.0.

makedepend only appear in the log at configure:

checking for makedepend... /usr/bin/makedepend

After install, nothing seems to be linked to it, which is not a
surprise, given its Introduction in BLFS. I don't know how tocheck this
in the static library, but would not expect any surprise.

As I had discussed also mozjs-24.2.0 in a ticket, it does not appear in
the logs for this version anywhere.

Run "make check" and the builds for 17 with and without makedepend in
the system, and noticed no difference but in the configure part.

Searched other distributions, and have some difficult finding it. IIRC,
only found in one page that was stating something like "this page is too
old..."

I may be wrong, but makedepend is a strong candidate for archive. If no
objections or if I have not committed mistakes in this analysis, this is
simple enough for me to do.

Now, about GLU. No strong feelings about it, but would prefer it to be
moved out of MESA. After I read what Armin wrote below, I think it is a
difficult job, I would prefer not being the one doing it. As I asked
Randy in the ticket, at least some clarification should be done why it
is in the book (I am not saying it should be removed or archived). I
trust very much in Igor's competence, in general, and in particular, for
this job (sorry for the burden, Igor).  :-)

> 
> The reason of why I left the package on the MESA page is that before
> MESA 9.0, GLU was part of MESA and thus all packages that depended on
> GLU itself depended on MESA directly or indirectly. You'd have to update
> the dependencies to depend on GLU afterwards, which I didn't had the
> time for. GLU itself, like GLUT depends on MESA only, no aditional deps
> required.
> 
> If you decide to split it, make sure you update the dependencies for
> some packages, which are yet unknown.
> 
> From archlinux reverse dependencies, following packages require GLU
> 
> xscreensaver
> libtiff
> libwebp
> freeglut (although it doesn't link to it. maybe it just requires its
> headers)
> libreoffice
> gnash
> jasper
> sdl
> xine-lib
> 

Thanks for the very important info, Armin.

I considered just xscreensaver, for the moment. In our book, it depends
on Xorg Applications and it is this one that depends on MESA. After
Igor's comment, Xorg Applications depends on MESA, but not GLU. So, it
should be replaced there. But xscreensaver, in anyway, should perhaps be
fixed already, because it depends on the X-Windows-System at runtime.

I was thinking that the move could be done in two stages. First one,
start pointing explicitly to GLU, after all done, stage tow, just move
GLU. Still, difficult for myself doing it.

-- 
[]s,
Fernando
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to