umbrello

[bertrand.zuchuat@…]

Hi,

Is it possible to add the umbrello software on macports:

​http://uml.sourceforge.net

Thanks

Bertrand

[ryandesign@…]

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.

[ryandesign@…]

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?

[snc@…]

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

[ryandesign@…]

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.)

[snc@…]

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

[ryandesign@…]

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

[snc@…]

Fixed in r69541.

[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

[ryandesign@…]

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} {

[snc@…]

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?

[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

[snc@…]

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.

[bertrand.zuchuat@…]

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.

[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.

[bertrand.zuchuat@…]

Crash log

[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?