| Summary: | new ebuild of yacas | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | tobias <tflorek> |
| Component: | New packages | Assignee: | George Shapovalov (RETIRED) <george> |
| Status: | RESOLVED FIXED | ||
| Severity: | trivial | CC: | harri, hypnos75, tflorek |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
ebuild
proteus-1.0.55.ebuild |
||
|
Description
tobias
2002-06-16 15:56:16 UTC
Created attachment 1555 [details]
ebuild
Hi Tobias. Thanks for subission. Re your note in the ebuild that installed yacas needed to compile gui: the correct solution would be to check yacas availability and bootstrap if necessary. I will get back to this submission some time later as other bugs/submissions will allow. If you want to speed up its processing you can take a look for example at dev-lang/ghc for ideas on how to bootstrap build and make necessary number of stages and modify your ebuild correspondingly. George Hi Tobias. Sorry, it's been a long time :( I decided to process the ebuild without waiting for the gui interface fix. I updated the ebuild to work with the current version - 1.0.54. I must say it took some effort to make it install allin a proper way ;). Anyway, the ebuild is in the tree (keymasked). Please test. Note to myself: add gmp and gsl support. George Two notes -- * Yacas requires gnuplot for plotting, but that is not asserted in the ebuild. * Cannot Proteus be implemented as a separate ebuild off the same tarball? Thanks for your effort ... I use MuPAD now, but it would it be nice to use something Free and therefore extensible. Hi Sourav. Thanks for your notes! >* Yacas requires gnuplot for plotting, but that is not asserted in the ebuild. Is this an absolute or optional dependency? yacas was working for me, but I was not trying to plot anything :). So, it looks like it is a run-time dependency, thus it may be added to RDEPEND. However it may be made to depend on some USE flag if its not always necessary.. >* Cannot Proteus be implemented as a separate ebuild off the same tarball? Perheaps. Since the gui has a special name it may be worth splitting it into separate ebuild, as opposed to build it based on some use flag, quite possibly the same used for adding gnuplot. Or it may be better to go the second route, what do you think? George >>* Yacas requires gnuplot for plotting, but that is not asserted in the ebuild. >Is this an absolute or optional dependency? yacas was working for me, but I was not >trying to plot anything :). >So, it looks like it is a run-time dependency, thus it may be added to RDEPEND. However >it may be made to depend on some USE flag if its not always necessary.. I suppose the choice could be implemented as a "local" USE flag, but I would default to having gnuplot instead of not having it -- plotting is core functionality, in my mind. >>* Cannot Proteus be implemented as a separate ebuild off the same tarball? >Perheaps. Since the gui has a special name it may be worth splitting it into separate >ebuild, as opposed to build it based on some use flag, quite possibly the same used >for adding gnuplot. Or it may be better to go the second route, what do you think? Proteus really is a separate app, but happens to be packaged with Yacas, so I think it would be better to make it a separate ebuild. Specificially, Proteus needs Yacas (and other things), but Yacas does not need Proteus. Hi Sourav.
>I suppose the choice could be implemented as a "local" USE flag, but I would >default to having gnuplot instead of not having it -- plotting is core >functionality, in my mind.
Well, I would try to avoid local falgs if we could use a global one. I tried to "ask around" yesterday, but seems that we do not have a eneric flag for this specific purpose. However there are two I could think about:
plotutils: used only by gnuplot to make it use plotutils. Technically this should be local flag, but as I understand it was implemented long before the split, so it made its way into use.desc then.
It might be changed to plot and made more generic.. However
1. its present purpose is quite specific and the change will not be completely logical in that repect
2. its not very known/visible, so it has high chances to be overlooked..
X: very major flag :) and what's more important, belongs to USE set in standard profile. Thus people who will not want X will have it explicitly turned off.
I need to mention, that I am hesitant to make yacas have gnuplot dependency by default, as yacas is completely functional in CLI and gnuplot will drag a lot of heavyweight stuff with it.. Rather I would like to avoid having any default if it can be avoided..
Therefore it looks like using "X" is the best approach from technical standpoint, - default profile will get gnuplot support and people who will not want it will have "-X" explicitly. The only problem is that this use does not directly relate to description "Adds support for XFree86", which I treat as optional support for some X interfaces. However in a more broad sence it is applicable, after all this is a function made possible under X :).
Thus I am leaning towards using "X" as a use f;ag in this case, but would like to ask for your opinion.
On proteus: Ok you convinced me :), I'll go about looking into producing the ebuild soon.
George
* X USE flag: That's probably the best option, since there isn't a "gnuplot" flag. Yacas and gnuplot can both be terminal-only programs. * Proteus: Yeah, I think people would be annoyed if all this X software got built; the X USE flag is even less appropriate for activating Proteus than above. Keep up the good work! Uf, its been a while, just a quick note, that 1.0.55 is out and is in portage and I makred 1.0.54 stable. Will try to get to the proteus... George Created attachment 14327 [details]
proteus-1.0.55.ebuild
An update.
1. I moved yacas into app-sci, not sure why it was committed into dev-lang
2. I tried to create the ebuild for proteus (DEPENDs on yacas), however there
is some problem with fltk - configure cannot find certain stuff. Can please
somebody, who has experience with both take a look? Like, is there specific
version that is necessary or anything?
Note that I did not yet touch src_install - will look at that function if
src_compile can be made to work.
George
Ok, proteus (and fltk) prove to be problemmatic and I don't have that much time on my hands now. Looks like will have to settle with plain yacas (which works). Whoever finds this and decides to do an ebuild, please just reopen the bug upon submission. Closing it for now. George |
