Summary: | MICO 2.3.13 ebuild (new package) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Malcolm MacLeod <mmacleod> |
Component: | New packages | Assignee: | Michael Haubenwallner (RETIRED) <haubi> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | federico.zenith, tommy |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
ebuild
patch patch |
Description
Malcolm MacLeod
2009-02-07 07:43:59 UTC
Created attachment 181222 [details]
ebuild
Created attachment 181223 [details, diff]
patch
Created attachment 181224 [details]
patch
I'm going to maintain mico-2.3.13 in main tree. The ebuild from sunrise overlay is broken in regards of the $(use_with) bits, their output doesn't apply to mico's configure (which is the real issue), because '--without-*' does not _disable_ a package, but actually _enables_ it using from path 'no'. It is disabled by default, and to keep it disabled, it needs to be configured "--with-*=<empty>". But thank you for the gcc-4.3 patches - although I haven'd tried them yet. *** Bug 250222 has been marked as a duplicate of this bug. *** *** Bug 229147 has been marked as a duplicate of this bug. *** Malcolm, do you by chance have some more experience in building/using mico? Some problems I encounter, and how I'm going to solve - (helpful) comments appreciated: Mico checks for some JavaCUP, but I don't know which version would suffice: Disabling search for JavaCUP. Bluetooth and wireless support both don't compile (due to upstream bugs), so I don't add use-flags and dependencies for them right now. Still need to report them. Although mico is coded for gtk-1, using a 'gtk-config' wrapper (seen in few other ebuilds) seems to work for using gtk-2. Use-flag 'qt3' adds dependency on qt-3. Also there is an option to add some X support: use-depending on x11-libs/libXt. Disabling ssl is only possible by presetting a config.cache variable. Don't know what terms 'snacc', 'smp' and 'SL3 AC support' mean (in mico-context), not enabling anyone of them. It isn't necessary to add '-fno-strict-aliasing' any more, mico knows about gcc-4 now. net-misc/mico-2.3.13 in cvs, keyworded ~x86 only. Hello Michael, I use mico for some small proprietary applications I maintain, I do not make use of some of the more advanced features though so a lot of them do not mean much to me. Just a note i forgot to mention, I am using this on an amd64 machine so keywording this ~amd64 should be okay. MICO optionally depends on javacup 0.10 so the 0.10k that is in portage should be okay, I do not think the functionality it provides is very important though so it might be best to just leave it disabled for now and add it if it becomes important at a later date. SL3 refers to "CORBA security level 3" as far as I know this adds interfaces and support for using CSIv2 and kerberos authentication with a CORBA ORB. I don't think mico yet supports kerberos with this only CSIv2 but I have never used this so I can't give any further details. snacc appears to be a compiler of sorts that generates c++ files from ASN.1 files, it is only needed/used if SL3 is enabled. snacc seems to be used to convert SMP into usable C++ code to be compiled. I am not even sure where to find the SMP library though so I would recommend just leaving the whole of SL3 disabled for now. If I delve into this stuff later I will follow up with more information. (In reply to comment #9) > Just a note i forgot to mention, I am using this on an amd64 machine so > keywording this ~amd64 should be okay. Re-added all the keywords found in old mico-2.3.11-r1.ebuild, so these now are: ~alpha ~amd64 ~ppc ~sparc ~x86 > MICO optionally depends on javacup 0.10 so the 0.10k that is in portage should > be okay, I do not think the functionality it provides is very important though > so it might be best to just leave it disabled for now and add it if it becomes > important at a later date. Strange: Have javacup-0.10k installed, but mico-configure is unable to detect this correctly. > SL3 refers to "CORBA security level 3" as far as I know this adds interfaces > and support for using CSIv2 and kerberos authentication with a CORBA ORB. I > don't think mico yet supports kerberos with this only CSIv2 but I have never > used this so I can't give any further details. > snacc appears to be a compiler of sorts that generates c++ files from ASN.1 > files, it is only needed/used if SL3 is enabled. snacc seems to be used to > convert SMP into usable C++ code to be compiled. I am not even sure where to > find the SMP library though so I would recommend just leaving the whole of SL3 > disabled for now. If I delve into this stuff later I will follow up with more > information. Ok, thank you! |