First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 119583
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo Science Related Packages <sci@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Peter Simons <simons@cryp.to>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 119583 depends on: Show dependency tree
Bug 119583 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2006-01-19 11:38 0000
Hi,

portage has Maude version 2.1.1, but the latest release available now is
version 2.2. Could someone please provide an EBUILD for the new version? It
would be very much appreciated. 

Peter

------- Comment #1 From Fredrik Normann 2006-02-15 04:44:03 0000 -------
I could look at it myself, but if someone more experienced would do it, please
step in. 

------- Comment #2 From Peter Simons 2006-07-30 02:48:41 0000 -------
Does anyone feel capable of accomplishing this task? I tried to patch the
existing 2.1.1 EBUILD for 2.2, but didn't succeed. The downloading of the files
is a bit of a pain, in part because the naming scheme at
http://maude.cs.uiuc.edu/download/ seems to have changed. It would be really
nice to have 2.2 in portage. There are some significant improvements over 2.2,
especially for users of core maude.

------- Comment #3 From Peter Simons 2006-10-24 13:45:06 0000 -------
Good news: Maude 2.2 used to crash gcc while building. The reason for this
problem are the SSP patches; when the flags

  -fno-stack-protector-all -fno-stack-protector

are appended to CFLAGS and CXXFLAGS, Maude 2.2 compiles just fine. I'll see
whether I find the time to produce an ebuild. It would be really nice if Gentoo
had the latest version of this fine tool.

------- Comment #4 From Peter Simons 2008-06-02 16:30:25 0000 -------
Good news: we are at Maude 2.3 by now.

The thing is this: in theory, I could provide an ebuild. I would like to,
actually, because I love Maude and would like to have it in portage. My
experience is, however, that every time I provided an ebuild for a tool that
the category maintainers apparently don't care about, it was ignored. So I had
essentially wasted my time. It's a pity, but that's my experience.

------- Comment #5 From Sébastien Fabbro 2008-06-02 23:20:30 0000 -------
Hi Peter,

> The thing is this: in theory, I could provide an ebuild. I would like to,
> actually, because I love Maude and would like to have it in portage. My
> experience is, however, that every time I provided an ebuild for a tool that
> the category maintainers apparently don't care about, it was ignored. So I had
> essentially wasted my time. It's a pity, but that's my experience.

Your time won't be wasted, our sci team we are just understaffed, and believe
me we maintain a whole lot of packages we do not use at all. 
If no one takes a look, I will later on. maude needs a serious bump and
cleanup.

------- Comment #6 From Markus Dittrich 2008-06-03 10:17:24 0000 -------
I'll bump it later. Maude-2.3 need some gcc-4.3 fixing
as far as I can tell.

cheers,
Markus 

------- Comment #7 From Markus Dittrich 2008-06-04 03:45:16 0000 -------
Ok, I've just committed maude-2.3. It seems to work from
what I can tell, but please let us know if there are any
issues since I don't know maude very well.

Two issues remain and I will have a look at them once I find
some time:

1) Some of the supplied tests fail (need to inform upstream)
2) maude-2.3 currently breaks with gcc-4.3 in more subtle
   ways than just missing header files. I'll have to have
   a closer look but this probably needs to be taken care
   of by upstream.

Best,
Markus

First Last Prev Next    No search results available      Search page      Enter new bug