|
OpenBSD Packages and Ports Installation and upgrading of packages and ports on OpenBSD. |
|
Thread Tools | Display Modes |
|
|||
Best moment to send a port update
Hi everyone,
Since the Lyx port seems not maintained anymore, I wrote an update myself: Code:
# pkg_info lyx|grep Maintainer Maintainer: The OpenBSD ports mailing-list <ports@openbsd.org> Thanks |
|
|||
|
|
||||
5.7 is set, and the ports tree was unlocked 15-Mar-2015. You are free to post your update.
However, if I recall correctly you're running 5.6. New port development and port updates must be done on -current. If you've developed your revisions on 5.6, you will need to test with -current, and your diffs must apply to the -current tree. The port is still maintained, even if it is an older release of Lyx. There have been two commits to the port since 5.6-release. |
|
|||
It's not unmaintained, it means that maintenance falls to the community rather than a specific individual. It's a subtle shifting of problem statement but I think it's a valuable one.
Great! Then the system works as intended. Consider taking maintainership of Lyx. |
|
||||
Debug and release preparation for 5.8 won't being until "-beta," which I predict (based on when -beta began for 5.6, 5.4, and 5.2) should occur in July. And if past performance is a predictor, the Project will continue with development of key features even during this period.
See FAQ 5.1 - OpenBSD's Flavors for a good explanation of the six-month release development cycle. Last edited by jggimi; 30th March 2015 at 10:07 AM. Reason: typo |
|
|||
Thank you all for your replies and your clarifications.
Jggimi, your memory is impressive! You're right I am running stable. But I installed -current on a spare (and slow) machine to make this update. In fact, there are very few changes and the port works both on 5.6 and -current. I'll send the update to the mailing-list. Thanks again Last edited by albator; 30th March 2015 at 11:55 AM. Reason: typo |
|
||||
I'm currently testing your submitted update on i386 since you have already tested on amd64. I'm on a second rebuild; the first time the package failed a lib-depends-check but I believe that was because I'd had the committed port installed when I built it. I then uninstalled and am currently rebuilding. I should be able to report results tomorrow.
Last edited by jggimi; 31st March 2015 at 03:12 AM. Reason: typo |
|
|||
Thanks Jggimi for testing this update.
This is my first modification to a port, and I might do things the wrong way. As my machine is very slow, here is what I did : - installed the current package with pkg_add. - deleted it with pkg_delete (no pkg_delete -a next). Which means all the dependencies are still there. - Installed the port with my changes. Last edited by albator; 31st March 2015 at 07:41 AM. Reason: typo |
|
||||
My i386 machine is even slower.
The lib-depends-check did fail properly. The updated tex2lyx program now requires devel/libmagic. I've added it as a LIB_DEPENDS and as a RUN_DEPENDS, and will let it rebuild. I've started a new build, but I won't be able to check its results until about 10 hours from now. |
|
|||
Here is an extract of Lyx 2.1.3 RELEASE-NOTES:
LyX now links against libmagic [...] if it is available at compile time. [...] The old builtin format detection code is used if libmagic is not available. Extract of configure: ### check for file magic support (currently optional) [...] lyx_warning_txt="$lyx_warning_txt == cannot find libmagic. Please check that the libmagic library is correctly installed on your system. Falling back to builtin file format detection. " lyx_warning=yes fi else lyx_warning_txt="$lyx_warning_txt == cannot find magic.h. Please check that the libmagic library is correctly installed on your system. Falling back to builtin file format detection. " lyx_warning=yes fi libmagic does not seem to be mandatory and is not installed on my system. magic.h is installed though, but this seems optional too: Code:
# find / -name "*libmagic*" /usr/ports/devel/libmagic /usr/ports/devel/py-libmagic # pkg_info|grep libmagic # # find / -name "*magic.h*" /usr/local/include/ImageMagick/magick/magic.h |
|
|||
You don't need both. LIB_DEPENDS is all you need.
Quote:
That is for something else. Don't play with it. |
|
||||
I'll guess that the optional library should be mandatory as it is available in the ports tree, and if tex2lyx works with it.
Ports are bulk built by the Project for -releases and -current. Those builds are done with dpb(1), so the specific mix of any independent packages that might be installed on any particular build machine in the server farm at build time cannot be predicted. We can only be assured of dependent packages. My assumption is the members want consistent builds with consistent results. Quote:
|
|
|||
Celeron M520. Damn, you win! Not by much though. And mine must get hotter ;-)
TDP: 2.5 W vs 30 W |
|
||||
Ho-kay. All done. Out of band, ibara recommended port-lib-depends-check over lib-depends-check. That recommended both LDEP and WANTLIB.
Code:
--- Makefile Mon Mar 30 19:21:51 2015 +++ makefile Tue Mar 31 18:37:08 2015 @@ -23,12 +23,13 @@ LIB_DEPENDS= ${MODQT4_LIB_DEPENDS}>=4.5.3 \ devel/boost \ + devel/libmagic \ textproc/enchant \ textproc/aspell/core WANTLIB += lib/qt4/QtGui>=8 aspell c m pthread stdc++ z WANTLIB += boost_regex-mt>=1 boost_signals-mt>=1 -WANTLIB += glib-2.0 gmodule-2.0 enchant +WANTLIB += glib-2.0 gmodule-2.0 enchant magic SEPARATE_BUILD= Yes USE_GMAKE= Yes I have never used .tex files, so I haven't a clue what to do with tex2lyx. Last edited by jggimi; 31st March 2015 at 11:27 PM. Reason: opyt |
|
|||
I started again from scratch, with no packages at all, to see if the same problem happens on amd64. It's been running for 14 hours... What is a good starting point before testing a port, should one delete all other related packages first? In this particular case, there wouldn't be many left.
Anyway you're right about adding libmagic. Is it better to send a new diff to ports@including the changes you've already sent? Before that, I will build it again with the new Makefile. Are you going to produce .tex files, so that you can use tex2lyx? Last edited by albator; 2nd April 2015 at 08:31 AM. Reason: clarirafication ;) |
|
||||
The Porter's Handbook doesn't explicitly recommend clean-slate building. It does say we need to know the software, and Step 26 of its Porting Checklist states:
Quote:
--- My machine is so slow that when I need to build a port, I install all build dependencies (if available) from packages: # pkg_add -az `make full-build-depends`
|
|
||||
I missed two questions.
Quote:
Quote:
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
unable to send external mail | Zyos | OpenBSD General | 11 | 17th November 2011 02:39 PM |
Send Syslogd To External Host | plexter | OpenBSD General | 2 | 18th July 2011 08:11 PM |
send mails with postfix | wesley | OpenBSD Packages and Ports | 1 | 18th August 2010 07:34 PM |
send files to email | milo974 | OpenBSD General | 7 | 1st September 2008 02:03 PM |
Send email to all local users | cajunman4life | FreeBSD General | 8 | 15th June 2008 10:52 AM |