Re: Battle for wesnoth
On 07/03/2018 17:38, David Marec wrote: > Hello, > > > Some days ago, the port games/wesnoth was removed from my poudriere > builds, because of boost libraries mismatches I guess. > > So that, I decided to port a newer version of the game (1.14.%) to > FreeBSD. If the port "works for me", it 'be better to provide a > port-tree compliant installation. > > If I'm running FreeBSD for years, it's the first time I am writing a > Makefile for the port tree. > > Thanks to the porters-handbook, (and the original wesnoth Makefile) > I was able to write a Makefile and provides a couple of patches. > One can find the files below: > https://gitlab.com/TurtleCrazy/wesnoth_1_14_freebsd > > Now, as a beginner, I have some questions regarding the Makefile to be > included in the port tree. > > First, the CMake file provides one option to disable the installation > of the game itself. > This might be use to run game servers only. It also avoid the > installation of SDL2 libs. > This option was not defined on the previous port, so I wonder if there > is a need for it. > > > It could be done by adding the following lines: > > GAME_DESC= The game client > GAME_CMAKE_OFF=-DENABLE_GAME=off > GAME_USE_SDL= image2 mixer2 net2 ttf2 sdl2 > > > > Second, the pkg-plist is missing. - what makes poudriere testport to > fail. - > > I did not find suitable information in the handbook that explains > how to fill it. Any clue may be helpful. > > > Next, some sets of options requires additional boost libraries. > as > * unit_test_framework > * iostreams program_options regex system thread random > > The Makefile need some reworks to allow fine-grained dependencies > > > Finally, what about the entry name in the port tree ? > > > > Feel free to correct the code, moreover: be "-pedantic". > > regards, > I can at least help on the pkg-plist file in the port directory: make makeplist cp work/.staged-plist pkg-plist you'll have to verify that everything's ok in it, but as long as you didn't do any plist substitutions, I think it'll be fine. -Joseph ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Battle for wesnoth
Hello, Some days ago, the port games/wesnoth was removed from my poudriere builds, because of boost libraries mismatches I guess. So that, I decided to port a newer version of the game (1.14.%) to FreeBSD. If the port "works for me", it 'be better to provide a port-tree compliant installation. If I'm running FreeBSD for years, it's the first time I am writing a Makefile for the port tree. Thanks to the porters-handbook, (and the original wesnoth Makefile) I was able to write a Makefile and provides a couple of patches. One can find the files below: https://gitlab.com/TurtleCrazy/wesnoth_1_14_freebsd Now, as a beginner, I have some questions regarding the Makefile to be included in the port tree. First, the CMake file provides one option to disable the installation of the game itself. This might be use to run game servers only. It also avoid the installation of SDL2 libs. This option was not defined on the previous port, so I wonder if there is a need for it. It could be done by adding the following lines: GAME_DESC=The game client GAME_CMAKE_OFF=-DENABLE_GAME=off GAME_USE_SDL= image2 mixer2 net2 ttf2 sdl2 Second, the pkg-plist is missing. - what makes poudriere testport to fail. - I did not find suitable information in the handbook that explains how to fill it. Any clue may be helpful. Next, some sets of options requires additional boost libraries. as * unit_test_framework * iostreams program_options regex system thread random The Makefile need some reworks to allow fine-grained dependencies Finally, what about the entry name in the port tree ? Feel free to correct the code, moreover: be "-pedantic". regards, -- David Marec https://lapinbilly.eu/ ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: What the port license should be when software is "free for non-commercial use" with "click-to-accept" or clickwrap license?
03.07.2018 14:06, Mathieu Arnold wrote: >>> But it doesn't ask to "agree" during 'pkg install dcc-dccd'. >> >> Yes. Meantime, you have several choices: >> >> 1) Mark the port NO_PACKAGE and/or no-pkg-mirror to force users use a port >> that > > It is not no-pkg-mirror, in this case, it is no-auto-accept. According to https://www.freebsd.org/doc/en/books/porters-handbook/licenses.html > no-pkg-mirror > Free redistribution of package is prohibited. Equivalent to setting > NO_PACKAGE. > The package will not be distributed from the FreeBSD package CDN > https://pkg.freebsd.org/. This is exactly what I'm talking about: preventing usage of a package because pkg(8) does not honor "no-auto-accept" yet. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Any way to prevent do-extract chmod and chown?
On 07/02/2018 16:50, Chris H wrote: > On Fri, 29 Jun 2018 00:05:59 +0200 "Mathieu Arnold" > said > >> On Thu, Jun 28, 2018 at 01:43:41PM -0400, Joseph Ward wrote: >> > Thank you. I found that to be the case; even though changing the >> > "do-extract" target successfully staged the files and directories with >> > the original permissions, pkg create seems to strip them out again >> > without the pkg-plist additions. >> > > Are you aware of an easy/already existing command to create the >> > pkg-plist with the user/group/permissions items for each file, or is >> > that a script I'm going to have to write manually? I'm currently >> using >> > the makeplist target as there are no subsitutions or anything else >> that >> > would screw up the default scenario. >> >> I am not aware of anything. But if you already have "stuff" creating a >> big hierarchy with many users and groups, it may be easier to adapt >> "stuff" to generate a pkg-plist file, or maybe to split your ports into >> smaller, more manageable bits. >> >> make makeplist will give you a correct listing of files and >> directories, but as everything runs as a regular user, it cannot be >> aware of the users/groups you intend on using in the plist. > make makeplist may be of help to you, as it would allow you to assign > ownership in > large chunks, thusly: > > @a:b:c > this > that > ... > theother > @d:f:e > somefile > ... > another > bunch > of > files > @other:owner:group:perms > thesefiles > ... > thosefiles > > This all assumes that the files are grouped as you need them tho. :-) > > HTH > > --Chris > >> >> -- >> Mathieu Arnold > > > ___ Unfortunately, they're not grouped together. What I'm doing (which is probably a little crazy) is turning jails into packages so that I can very easily upgrade them on my remote systems. So I have a basejail package which is the dependency for my smtp-jail package, which includes the mounts into the basejail, etc. So it's essentially the freebsd base permissions (and subsets for the thin jails) which of course aren't grouped at all, and also involves thousands of files. I ended up using mtree (as suggested by Freddie Cash), having the build system that creates the jails and their dist-files take the mtree spec for the jail and include it in the package, and then as a pkg-post-install script I made it put the permissions back via mtree -u. My other option was to take the makeplist target and alter it. I found the generate_plist() function in Mk/Scripts/check-stagedir.sh, which uses find and sed to create the plist. I was going to add a "stat" in there, with the formatting of stat -f "@(%Su,%Sg,%OMp%OLp) %N" so that I ended up with the plist with the correct permissions on every file. I'm pretty sure that would have worked, but the mtree solution suggested by Freddie worked really well, so I just stuck with it. -Joseph ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Passenger not working any more after Base System upgrade: can you reproduce?
On 02.07.2018 03:19, José Pérez via freebsd-ports wrote: > Hi, > after a Base System upgrade Passenger fails on > startup with this error: > nginx: [alert] Unable to start the Phusion Passenger watchdog: it seems > to have been killed with signal SIGABRT during startup (-1: Unknown > error) > > Can please someone try and reproduce and/or > suggest a workaround/fix? > > How to reproduce: > - stable 11.2 > - install nginx or apache (same problem with >both) > - install (almost) any passenger version (I >could reproduce with 5.2.1, 5.3.2 (current >in ports) and 5.3.3 (latest)) > > What you get: > # service nginx start > Performing sanity check on nginx configuration: > nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is > ok > nginx: configuration file /usr/local/etc/nginx/nginx.conf test is > successful > Starting nginx. > nginx: [alert] Unable to start the Phusion Passenger watchdog: it seems > to have been killed wit > > Further error details in log: > [ pid=57456, timestamp=1530359790 ] Process aborted! signo=SIGABRT(6), > reason=#65543, si_addr=0x0, randomSeed=1530359790 Have your tried to google this? Search for "reason=" "65543" gives https://github.com/phusion/passenger/issues/987 as second link that mentiones very similar problem pointing to some C++ compiler incompatibility and FreeBSD 11.2 got new clang version 6.0.0, so that may be a culprit. You should try to deinstall all dependent ports including nginx and the application itself and rebuild them all from scratch to eliminate possible C++ mangling/runtime problems. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Passenger not working any more after Base System upgrade: can you reproduce?
El 2018-07-03 09:59, Eugene Grosbein escribió: On 02.07.2018 03:19, José Pérez via freebsd-ports wrote: [skip] Have you actually read the log? Further error details in log: [ pid=57456, timestamp=1530359790 ] Process aborted! signo=SIGABRT(6), reason=#65543, si_addr=0x0, randomSeed=1530359790 [ pid=57456 ] Crash log dumped to /var/tmp/passenger-crash-log.1530359790 [skip] *** ERROR: cannot execute lsof: No such file or directory (errno=2) Make sure your lsof binary is present (installed by port or package) and your application has correct search path for it. Hi, this is completely irrelevant because lsof is needed to handle the aborting Passenger application. Even if you have lsof in path, Passenger still fails! Furthermore there is a bug in Passenger source when it tries to use ls -v option which is absent in BSDs, but the source reads: // The '-v' is for natural sorting on Linux. On BSD -v means something else but it's harmless. Well, not so harmless as we can see: ls: illegal option -- v usage: ls [-ABCFGHILPRSTUWZabcdfghiklmnopqrstuwxy1,] [-D format] [file ...] ERROR: Could not run 'ls' to dump file descriptor information! The problem is difficult to dig because is independent from Passenger version and dependent on FreeBSD Base System version. Regards, -- José Pérez ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Passenger not working any more after Base System upgrade: can you reproduce?
On 02.07.2018 03:19, José Pérez via freebsd-ports wrote: [skip] Have you actually read the log? > Further error details in log: > [ pid=57456, timestamp=1530359790 ] Process aborted! signo=SIGABRT(6), > reason=#65543, si_addr=0x0, randomSeed=1530359790 > [ pid=57456 ] Crash log dumped to > /var/tmp/passenger-crash-log.1530359790 [skip] > *** ERROR: cannot execute lsof: No such file or directory (errno=2) Make sure your lsof binary is present (installed by port or package) and your application has correct search path for it. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: conflicts with packages on install
On Tue, Jul 03, 2018 at 11:29:05AM +0800, blubee blubeeme wrote:
> I'm working on updating a port it currently installs in a
> ${PREFIX}/${PORTNAME}/bin and I'd like to create symlinks t ${PREFIX}/bin
>
> The issue i'm running into is that there's a binary file "terrain" this
> conflicts with graphics/mesa-demos/terrain.
>
> I'm looking for options on resolving this conflict, any suggestions?
Change the name of the file?
--
Mathieu Arnold
signature.asc
Description: PGP signature
Re: What the port license should be when software is "free for non-commercial use" with "click-to-accept" or clickwrap license?
On Tue, Jul 03, 2018 at 06:33:43AM +0700, Eugene Grosbein wrote: > 03.07.2018 6:17, Yuri wrote: > > >> It does. See mail/dcc-dccd for example. > > But it doesn't ask to "agree" during 'pkg install dcc-dccd'. > > Yes. Meantime, you have several choices: > > 1) Mark the port NO_PACKAGE and/or no-pkg-mirror to force users use a port > that It is not no-pkg-mirror, in this case, it is no-auto-accept. > 1a) builds software from source, or > 1b) installs pre-build binaries bundled with distfiles (just like cvsup > binary port did earlier); > 2) Prepare and submit a patch for pkg itself to support this feature. It > should be not hard to do. > > > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > -- Mathieu Arnold signature.asc Description: PGP signature
