SliTaz SliTaz Forum

You are not logged in.

#1 2012-03-01 22:08:53

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

ot thanks to the unknown enthusiast - cooking latex

How can I find out who was the unknown enthusiast who tried to cook latex? I see the packages is broken, but the effort was there and this a reason to recognize it! ;-)

Offline

#2 2012-03-02 09:50:19

totoetsasoeur
Moderator
Registered: 2011-03-29
Posts: 247

Re: ot thanks to the unknown enthusiast - cooking latex

Just have a look at the receipt.

It says:

MAINTAINER="pascal.bellard@slitaz.org"

So Bellard is the one.

Cheers.

Offline

#3 2012-03-02 10:00:30

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: ot thanks to the unknown enthusiast - cooking latex

@pascal bellard

I want to thank you for the trial to create a texlive package for Slitaz. As a non-technician I cannot understand why it failed - but hopefully, not in this second, you find time to tell why it failed and whether something can be done to get a working package out of it. There are 3 packages in cooking now that are ready, can be fired up, but lack the ,,motor".

TeXmacs-1.0.7.8.tazpkg and texinfo-4.13a.tazpkg and gummi-0.6.1.tazpkg

(No, sorry, I cannot compile, does not fit to my brain and is normally just a waste of time and ressources- ,,non-technician" is true)

All I can do is thorough testing and give feedback.

Offline

#4 2012-03-02 10:37:43

bellard
Administrator
Registered: 2011-03-28
Posts: 657

Re: ot thanks to the unknown enthusiast - cooking latex

In http://cook.slitaz.org/undigest/cooker.cgi?pkg=latex

The failure is:

mv: can't rename 'ft-install/lib/libttf.a': No such file or directory

Likely because the library was installed in a wrong directory:

/usr/bin/install -c .libs/libttf.a /usr/lib/libttf.a

The receipt http://cook.slitaz.org/undigest/cooker.cgi?receipt=latex must be updated.

Maybe with a ./configure argument, a BUILD_DEPENDS complement, or a patchfile ?

The undigest wok holds unfinished packages. Everybody can improve them. Fill free to improve it.

See http://www.slitaz.org/en/doc/ and http://doc.slitaz.org/

Offline

#5 2012-03-02 11:37:58

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: ot thanks to the unknown enthusiast - cooking latex

Thanks for the quick answer, Pascal!

But unfortunately I did not lie. I a biology and geography teacher and I move into technical details to that amount that I can get the desired functionality. IT-technique is kind of alien for me.

,,(No, sorry, I cannot compile, does not fit to my brain and is normally just a waste of time and ressources- ,,non-technician" is true)

All I can do is thorough testing and give feedback."

Therefore this

   http://cook.slitaz.org/undigest/cooker.cgi?receipt=latex

is beyond my scope. How do you estimate the amount of work to get a running package that one can use under Slitaz? In another thread I gave the argument that such a thing cannot be a regular part of Slitaz, just for the demand of space. But when a pupils likes Slitaz he normally wants to install it on his harddrive. Then there is not such a RAM problem and not that space problem. I use a machine with 1 GB RAM and after installing the developer tools I cannot use tazlito writefs. No space left.

It is not urgent but I would like to hear your opinion.

The next left open question is this kompozer: it works with Slitaz 2.0 and 3.0 but not with cooking and not with 4.0 devel (what I use with great pleasure). It is a *.tar.gz-software that runs from a script. But not with cooking. All I can state is that it does not work. - It is an easy nice-looking piece of an html-editor - and it is platform-independent, which is very important in a school environment. This is absoletly dominated by Microsoft to a ridiculous amount, but Apple is gaining ground quick and starts to increase our problems in having a platform-independent communication with our boxes.

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.016 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]