Opened 9 years ago

Closed 9 years ago

#25454 closed request (worksforme)

umbrello

Reported by: Garfield-fr (Bertrand Zuchuat) Owned by: nerdling (Jeremy L)
Priority: Normal Milestone:
Component: ports Version: 1.9.1
Keywords: Cc: nerdling (Jeremy L), sharky@…, ryandesign (Ryan Schmidt)
Port: kdesdk4

Description

Hi,

Is it possible to add the umbrello software on macports:

http://uml.sourceforge.net

Thanks

Bertrand

Attachments (2)

drkonqi.png (36.8 KB) - added by Garfield-fr (Bertrand Zuchuat) 9 years ago.
crash_log.txt (28.5 KB) - added by Garfield-fr (Bertrand Zuchuat) 9 years ago.
Crash log

Download all attachments as: .zip

Change History (20)

comment:1 Changed 9 years ago by drkp (Dan Ports)

Port: umbrello added
Type: enhancementrequest

comment:2 Changed 9 years ago by ryandesign (Ryan Schmidt)

The web site says "Umbrello 2.0 is part of the kdesdk module in KDE 4.0.0." That means it should be part of the kdesdk4 port we already have in MacPorts.

comment:3 Changed 9 years ago by ryandesign (Ryan Schmidt)

Cc: snc@… sharky@… ryandesign@… added
Port: kdesdk4 added; umbrello removed
Summary: Umbrello on portumbrello

Also, you appear to need to use the kdesdk4 port's +no_boost variant to get umbrello.

My question for the maintainers of kdesdk4, then, is: if disabling boost enables umbrello, what advantage does enabling boost confer?

comment:4 Changed 9 years ago by nerdling (Jeremy L)

The kdesdk4 CMake file says that boost is required to build Umbrello.

comment:5 in reply to:  4 Changed 9 years ago by ryandesign (Ryan Schmidt)

Replying to snc@…:

The kdesdk4 CMake file says that boost is required to build Umbrello.

But the Portfile does the opposite of that. (It removes the boost dependency to build umbrello.)

comment:6 Changed 9 years ago by nerdling (Jeremy L)

Ah, I see now. Remnant of when it was +boost instead of +no_boost. I'll fix that shortly.

comment:7 Changed 9 years ago by ryandesign (Ryan Schmidt)

Probably the variant should become +boost again (+no_* variants should be phased out now that MacPorts 1.9+ records negative variants in the registry).

comment:8 Changed 9 years ago by nerdling (Jeremy L)

Owner: changed from macports-tickets@… to snc@…
Status: newassigned

comment:9 Changed 9 years ago by nerdling (Jeremy L)

Resolution: fixed
Status: assignedclosed

Fixed in r69541.

comment:10 Changed 9 years ago by Garfield-fr (Bertrand Zuchuat)

What's the correct commandline to install Umbrello with kdesk4 ?

I tested with: port install kdesk4

but i don't have umbrello.

Thank's for your help

comment:11 in reply to:  10 ; Changed 9 years ago by ryandesign (Ryan Schmidt)

Replying to bertrand.zuchuat@…:

What's the correct commandline to install Umbrello with kdesk4 ?

sudo port install kdesdk4 +boost

Jeremy, the patchfile can be deleted now, right? since the port isn't using it anymore?

I still wonder about the variant name and its description.

variant boost description {Required to build Umbrello} {

I would have preferred something like:

variant boost description {Use Boost (required to build Umbrello)} {

Does adding Boost to the build serve any purpose other than enabling the build of Umbrello? If not, would "umbrello" be a better/clearer variant name choice?

variant umbrello description {Build Umbrello} {

comment:12 in reply to:  11 Changed 9 years ago by nerdling (Jeremy L)

Replying to ryandesign@…:

Jeremy, the patchfile can be deleted now, right? since the port isn't using it anymore?

It's already deleted.

I still wonder about the variant name and its description. I would have preferred something like: `variant boost description {Use Boost (required to build Umbrello)} Does adding Boost to the build serve any purpose other than enabling the build of Umbrello? If not, would "umbrello" be a better/clearer variant name choice? variant umbrello description {Build Umbrello}

I'll happily entertain changing the description.

Umbrello itself uses more than just boost but it's the only thing I block in the dependency tree because it can be such a pain to build. I generally follow the kitchen sink perspective except for when a painful build is involved. It's along this line that I decided to use package names for variants, like x11 and qt4: it's to avoid building the package across all installs. An argument can also be made for granular control of what is built. Do you think it's more important to aid a user from installing a package or making variants reflect precisely what they do?

comment:13 in reply to:  11 Changed 9 years ago by Garfield-fr (Bertrand Zuchuat)

I ran the command

sudo port install kdesdk4 +boost

but i don't have Umbrello in my commandline. Why ?

Thank's for your help

comment:14 Changed 9 years ago by nerdling (Jeremy L)

Umbrello is a GUI application. From their SourceForge site:

Running the Program

After you have installed the program, you can run the program from the menu option Development -> Umbrello.

Changed 9 years ago by Garfield-fr (Bertrand Zuchuat)

Attachment: drkonqi.png added

comment:15 Changed 9 years ago by Garfield-fr (Bertrand Zuchuat)

Resolution: fixed
Status: closedreopened

Hi,

After install of kdesdk4 and option boost, i launch umbrello but i have this error (show file drkonqi). Where's possible to resolve this error ?

Thanks for your support.

comment:16 Changed 9 years ago by sharky@…

Could you please provide the crash information? You can get this information by clicking on the "Report" button ("Signaler" in your case), then copying the provided text.

Changed 9 years ago by Garfield-fr (Bertrand Zuchuat)

Attachment: crash_log.txt added

Crash log

comment:17 Changed 9 years ago by sharky@…

Look at the following:

libSystem.B.dylib                   0x00007fff831ca972 abort + 83
QtCore                              0x0000000100e3c245 qt_message_output(QtMsgType, char const*) + 117
libkdeui.5.dylib                    0x0000000100597652 KApplicationPrivate::init(bool) + 2066

The fact that "abort" gets called implies that qt_message_output() was called with the "QtFatalMsg" message type. I took a look at KApplicationPrivate::init() and unless I am mistaken, the most likely explanation is the "kFatal" is being called here:

  if (!QDBusConnection::sessionBus().isConnected() || !(bus = QDBusConnection::sessionBus().interface())) {
      kFatal(101) << "Session bus not found" << endl;
      ::exit(125);
  }

=> is DBus activated / working for you?

comment:18 Changed 9 years ago by nerdling (Jeremy L)

Resolution: worksforme
Status: reopenedclosed
Note: See TracTickets for help on using tickets.