Scribus-devel 1.3.5.1

[Veence (Vincent)]

The following Portfile builds the new Scribus 1.3.5.1 with some options. I feel this version should be placed in a separate port, because the code has been extensively rewritten and the dependencies have extensively changed (e.g. Qt4 instead of Qt3).

But, note the following remarks:

1. For an unknown reason, libpodofo is incorrectly referenced in the executable and two plugins. This is taken care of by a special patch, but I will report it upstream to have it at least examined and at best fixed;

2. The 64-bit version seems to be plagued by a bug (on SL?): vertical lines (be they graphic or part of glyphs/letters) are incorrectly displayed. Solid lines are replaced by a heap of triangles. I can't figure out where the bug is. This does not happen in the 32-bit version, so it is – at least for now – greatly recommended to launch the application in 32-bit mode, but that won't be possible if you havn't compiled the dependencies with the universal variant. Please can you confirm the bug?

Otherwise, enjoy!

[Veence (Vincent)]

Darn. There was a slight bug in the first Portfile, I'm attaching a correct one. Please note I have not tested the build without application bundle.

[ryandesign (Ryan Carsten Schmidt)]

Some notes:

• "bin:bin/foo:bar" is not valid syntax. You want "path:bin/foo:bar".
• Your long_description has nonbreaking spaces in it, and appears to be missing newlines after some of its backslashes.
• Your Portfile is using tabs, at 2-spaces-per-tab indentation. The existing scribus port is using spaces, with columns at multiples of four spaces, which is what we prefer.
• You said this should go in a new port, but you still called the port scribus. I don't think I would make it a new port. Or is there a compelling reason why someone would prefer to use the older version?
• Whether or not this will be a new port or update the existing one, your update should not make unrelated whitespace changes, otherwise it's difficult to see what functional changes were made. If you want whitespace changes made, we can do that, but in a separate commit that does nothing but change the whitespace. (But changing spaces to tabs is not acceptable because we want to move ports toward using spaces, not away from them.)

[Veence (Vincent)]

Ok for bin:bin/foo:bar (but this is not explicit in the documentation); the missing newlines is probably an artefact of Textwrangler (which folds long lines even without newline endings), I will be more careful next time. Besides, for the white spaces, this wasn't meant to be an update from scribus 1.3.3, but rather a new branch, so I used a brand new spacing scheme. This port *MUST* not be committed in lieu of the old one: scribus 1.3.5.1 is plenty of bugs, which makes it barely usable (or experimental): even PDF export seems faulty. Normal users should thus stick to the old stable branch, or expect very poor results. I should have added that to the description, but I was busy elsewhere.

[ryandesign (Ryan Carsten Schmidt)]

Ok, we could call it scribus-devel then, to indicate it is an unstable development version.

[Veence (Vincent)]

It seems a reasonable course :) I've sent a message to the scribus team asking if they actually tested it on SL, because I cannot imagine how they could actually release the code with such a great number of bugs.

Besides, the hardest problem is #21459: qt3 is not SL compatible, and therefore scribus 1.3.3 won't build on SL, leaving no other choice than 1.3.5.1.

[ryandesign (Ryan Carsten Schmidt)]

Replying to vince@…:

Ok for bin:bin/foo:bar (but this is not explicit in the documentation)

Thanks for pointing that out. I have corrected the documentation in r58044.

[nerdling (Jeremy Lavergne)]

This is more of a submission than an update …

[nerdling (Jeremy Lavergne)]

scribus-devel, cleaned whitespace

[nerdling (Jeremy Lavergne)]

Is there a particular reason that you have use_configure no and then set the configure phase?

[nerdling (Jeremy Lavergne)]

Cc Me!

[Veence (Vincent)]

Replying to snc@…:

Is there a particular reason that you have use_configure no and then set the configure phase?

The configure phase is handled by cmake: it exists, but does not rely on the standard configure tool. Note that the whole file can seem a bit awkward. I have a much better solution in terms of Portfile on an upcoming port (qgis) that I shall submit today or tomorrow. Briefly, it consists in redefining configure.cmd in cmake and then proceed with cmake options as standard configure.args.

[anddam (Andrea D'Amore)]

vince, are there any reason why you did not commit the port anymore?

I was looking to update scribus port and found this, btw I did the same with use_configure and ad-hoc configure fase, now I'm going to look at qgis to check your better solution.

[anddam (Andrea D'Amore)]

Cc Me!

[Veence (Vincent)]

Scribus 1.3.5 is totally outdated (1.3.9 is the current version). I am currently working on another update, but as soon as I finished, I'll try to set up a portfile for the current version of scribus.

[Veence (Vincent)]

I have submitted 1.3.9 (1.4.0 is coming soon), so I close all this.

[su-v]

Replying to vince@…:

I have submitted 1.3.9 (1.4.0 is coming soon), so I close all this.

Vince, would you consider modifying the port description as well? It currently still says "X11-based WYSIWYG desktop publishing application". Or is Scribus indeed installing/depending on qt4-x11 (outdated, as far as I understand)?

[Veence (Vincent)]

That's done in r76941.