-
Notifications
You must be signed in to change notification settings - Fork 764
/
Copy pathCHANGES
4292 lines (3081 loc) · 143 KB
/
CHANGES
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
Updating Information for FreeBSD ports developers
This file is maintained by [email protected] and copyrighted by the
FreeBSD Foundation.
This file contains major changes to ports and the ports infrastructure.
Intended audience are ports committers, maintainers and other
developers. User oriented changes should be submitted for inclusion
in the release notes and/or placed into UPDATING.
All ports committers are allowed to commit to this file.
20250203:
AUTHOR: [email protected]
Following legacy variables are removed from Mk/Uses/samba.mk
* SAMBAPORT
* SAMBAINCLUDES
* SAMBALIBS
And ones below should be used instead.
* SAMBA_PORT
* SAMBA_INCLUDEDIR
* SAMBA_LIBDIR
20241231:
AUTHOR: [email protected]
Convert bsd.java.mk to USES
The following features have been added or changed:
- Instead of USE_JAVA use USES=java. This defaults to
USES=java:build,run if NO_BUILD is undefined. Else it defaults to
USES=java:run
- Instead of USE_ANT=yes use USES=java:ant which also implies
USES=java:build
- Instead of JAVA_BUILD=yes use USES=java:build. Does not imply run or
extract
- Instead of JAVA_EXTRACT=yes use USES=java:extract does not imply
build or run
- Instead of JAVA_RUN=yes use USES=java:run does not imply extract or
build
- Instead of USE_JAVA=<version> use USES=java and JAVA_VERSION=<version>
20241231:
AUTHOR: [email protected]
Converted remaining bsd.ocaml.mk to Uses/ocaml.mk
- Instead of USE_OCAML=yes use USES=ocaml. If empty USES=ocaml implies
build and run
- Instead of USE_OCAMLFIND_PLIST use USES=ocaml:findplist which also
implies USES=ocaml:findlib
- Instead of USE_OCAML_CAMLP4 use USES=ocaml:camlp4
- Instead of USE_OCAML_FINDLIB use USES=ocaml:findlib
- Instead of USE_OCAML_LDCONFIG use USES=ocaml:ldconfig
- Instead of USE_OCAML_WASH use USES=ocaml:wash
- Instead of NO_OCAML_BUILDDEPENDS use USES=ocaml:run
- Instead of NO_OCAML_RUNDDEPENDS use USES=ocaml:build
- Instead of USE_OCAML_TK use USES=ocaml:tk which actually implies
USES=ocaml:tkbuild and USES=ocaml:tkrun
- Instead of NO_OCAMLTK_BUILDDEPENDS use USES=ocaml:tkrun
- Instead of NO_OCAMLTK_RUNDEPENDS use USES=ocaml:tkbuild
- USES=ocaml:dune remains unchanged
- Prepare to add/remove keywords easily
20240408:
AUTHOR: [email protected]
A new variable DBD_MYSQL has been introduced and should be used to depend
on the correct version of p5-DBD-mysql. Versions >= 5.000 removed support
for MariaDB. DBD_MYSQL will check which MYSQL_FLAVOUR is used and set the
correct version as a dependency. For this to work, ports need to add mysql
to USES.
20240408:
AUTHOR: [email protected]
USES=cmake now supports `indirect' argument. This argument adds cmake binary
to the BUILD_DEPENDS and and exposes CMAKE_ARGS and some other helpers, but
does not run cmake in the configure step. cmake:indirect is intended
primarily for ports which use meson or pep517 for build.
20240229:
AUTHOR: [email protected]
A new command SETENVI that clears the environment and a new variable
WRK_ENV that contains a basic environment to use with SETENVI have
been added.
Ports that run (parts of) the upstream build system directly using
commands like "${SETENV} ${MAKE_ENV} ${MAKE_CMD} ..." should change
that to "${SETENVI} ${WRK_ENV} ${MAKE_ENV} ${MAKE_CMD} ...". This way
the build system runs with a clean environment without interference
from the user environment or ports framework environment. Ports can
add extra environment variables to WRK_ENV similar to CONFIGURE_ENV,
MAKE_ENV, TEST_ENV, and so on, but WRK_ENV is used in all targets
while the latter are target-specific.
20240111:
AUTHOR: [email protected]
MAN[1-8LN]PREFIX variable has been removed from the framework, use PREFIX
directly.
20230929:
AUTHOR: [email protected]
USE_PYTHON=cryptography{,_build,_test} has been added to the ports tree.
20230722 entry is obsoleted now. All existing USES=pycryptography* have
been converted to USE_PYTHON=cryptography{,_build,_test} in PR 273727.
Usage:
USE_PYTHON=cryptography_build adds security/py-cryptography to BUILD_DEPENDS
USE_PYTHON=cryptography adds security/py-cryptography to RUN_DEPENDS
USE_PYTHON=cryptography_test adds security/py-cryptography to TEST_DEPENDS
20230823:
AUTHOR: [email protected]
USES=llvm.mk now supports 'export' (default) and 'noexport' arguments.
When export is set, CC, CXX and CPP will be set to the path corresponding
to the chosen llvm-version.
20230821:
AUTHOR: [email protected]
A new uses 'ebur128' has been added to transparently depend on the
proper variant of 'rust' or 'legacy' depending on the default version
set by the user.
Usage: USES=ebur128:ARGS
Valid ARGS: <none>, build, lib, run, test
<none>: (default) same as lib
build: add BUILD_DEPENDS
lib: add LIB_DEPENDS
run: add RUN_DEPENDS
test: add TEST_DEPENDS
If you prefer not to use rust, add the following to your make.conf:
DEFAULT_VERSIONS+=ebur128=legacy
20230728:
AUTHOR: [email protected], [email protected]
A new uses 'guile' has been added to transparently depend on the
proper variant of guile depending on the default version set by the
user and the demands of the port.
See Mk/Uses/guile.mk for in-depth documentation.
20230722:
AUTHOR: [email protected]
A new uses 'pycryptography' has been added to transparently depend on the
proper variant of 'rust' or 'legacy' depending on the default version set
by the user.
Supported arguments: <none>,build,run
Passing no arguments (<none>) is equivalent to passing both build and run.
Usage:
USES=pycryptography:build
-> adds a BUILD_DEPENDS only
USES=pycryptography:run
-> adds a RUN_DEPENDS only
USES=pycryptography:test
-> adds a TEST_DEPENDS only
USES=pycryptography:build,run or USES=pycryptography
-> adds a BUILD_ and RUN_DEPENDS
20230712:
AUTHOR: [email protected]
USE_GITLAB has been changed to allow fetching by tag name. This was done by
removing the GL_COMMIT variable and introducing GL_TAGNAME instead.
Similar to USE_GITHUB/GH_TAGNAME, you can still use a commit hash with
GL_TAGNAME (the full 40-character hash is required for that). If not
specified, GL_TAGNAME defaults to DISTVERSIONFULL.
Note fetching by tag name might not work on gitlab installations running
very old versions; in that case, you must still specify a commit hash.
For now, GL_COMMIT is still recognized but deprecated, using it will issue
a warning in developer mode.
20230712:
AUTHOR: [email protected]
Two new targets are now available: fetch-url-recursive-list
and fetch-urlall-recursive-list. They are the recursive variants
of the well-established targets fetch-url-list and fetch-urlall-list,
which allow for listing the complete URLs of DISTFILES and PATCHFILES
of a port. The recursive variants add the URLs of the port's dependencies
to the output.
20230430:
AUTHOR: [email protected]
USES=magick has been updated based on flavorized ports.
A new argument 'x11' is available to specifically depend on the flavor
with X11 support. Fallback to DEFAULT_VERSIONS now happens
independently for the version (currently 6 or 7) and the flavor
(currently x11 or nox11).
Only use arguments for version or flavor if your port really requires
it. Also, there is no need to add options for selecting the -nox11
flavor any more, as the user setting in DEFAULT_VERSIONS will be
honored.
20230111:
AUTHOR: [email protected]
USE_PYTHON=pep517 has been added to facilitate building using the
new format.
USE_PYTHON=pep517 takes no arguments. Operation is similar to
USE_PYTHON=distutils, although the build backend specified in
pyproject.toml shall be specified in BUILD_DEPENDS.
A usage guide and implementation primer is available at:
https://wiki.freebsd.org/Python/PEP-517
20221217:
AUTHOR: [email protected]
USES=llvm has been added to more easily depend on llvm.
USES=llvm supports two kinds of arguments:
* mode
<none>: defaults to build
build: add a BUILD_DEPENDS on chosen llvm-port
run: add a RUN_DEPENDS on chosen llvm-port
lib: add a LIB_DEPENDS on chosen llvm-port
* version
<none>: defaults to ${LLVM_DEFAULT}
number: use explicitly the specified version
min=number: use specified min if ${LLVM_DEFAULT} is lower
max=number: use specified max if ${LLVM_DEFAULT} is higher
An example usage might be:
USES= llvm
or
USES= llvm:13,build
or
USES= llvm:min=14,lib
The following variables are exposed to be used in the ports tree at the moment:
* LLVM_VERSION version chosen from the arguments to llvm.mk
* LLVM_PORT chosen llvm port
* LLVM_CONFIG llvm-config of the chosen port
* LLVM_LIBLLVM libLLVM.so of the chosen port
* LLVM_PREFIX installation prefix of the chosen port
20221026:
AUTHOR: [email protected]
3 new features are available now: PIE, RELRO, BIND_NOW, each port can
specify the inability to support any via <feature>_UNSAFE
All 3 are off by default, the intent is to activate following the freebsd
base activation of the same features.
End users can activate/deactivate globally via WITH_/WITHOUT_ <feature>
20221014:
AUTHOR: [email protected]
USES=luajit has been added to support a unified luajit version. The
default here is luajit-devel, which should be the right version for
nearly everybody.
luajit-openresty is a drop-in replacement for anything that luajit-devel
works in, though not necessarily the other way around. If a program uses
the openresty-specific API then you will need USES=luajit:luajit-openresty.
The standard USES for most ports:
USES=luajit
For anything that requires the openresty API:
USES=luajit:luajit-openresty
20220911:
AUTHOR: [email protected]
kde.mk, qt.mk and pyqt.mk now use a colon for component suffixes
Suffixes for build, run and test (for pyqt) dependencies used an underscore
previously. This was not in line with most other USES, using a colon for
that purpose.
So if you previously had for example
USE_QT= buildtools_build
replace it with
USE_QT= buildtools:build
20220907:
AUTHOR: [email protected]
The convention of a WWW: line at the end of each port's pkg-descr file
has been changed to a WWW= definition in the port's Makefile. All ports
have been converted to follow this new scheme.
The portlint and portfmt ports will be updated, but may erroneously flag
the new convention as incorrect until the new versions have been installed.
20220826:
AUTHOR: [email protected]
A new Uses for 'vala' has been added.
To depend on libvala, use
USES=vala:lib
to only add a build-time dependency, use
USES=vala:build
20220821:
AUTHOR: [email protected]
qt.mk now supports both Qt 5 and Qt 6.
To make use of Qt6 write:
USES=qt:6
USE_QT=list of Qt6 components
Please take a look at qt.mk to see the available components.
20220722:
AUTHOR: [email protected]
'Created by' are being removed from the ports makefiles.
Created by lines have historically been used to attribute contributions
to the original creators of the ports. However, those might no longer
be contributing to the port
20220430:
AUTHOR: [email protected]
A new USES has been added to handle dependency on gstreamer.
Instead of writing
USE_GSTREAMER1=[list of components]
you now have to write
USES=gstreamer
USE_GSTREAMER=[list of components]
If your port previously set just
USE_GSTREAMER=yes
this now is simply
USES=gstreamer
20220415:
AUTHOR: [email protected]
A new USES has been added to handle testing with pytest.
USES= pytest
Introduces dependency on pytest and adds do-test target which calls
pytest with the right environment and arguments.
Additionally, PYTEST_{IGNORED,BROKEN}_TESTS knobs are provided for
skipping failing tests in a convenient and documented way.
20220218:
AUTHOR: [email protected]
A new USES has been added to change an ELF binary's feature control note.
USES= elfctl
ELF_FEATURES= +noaslr,wxneeded:foo \
-noprotmax:foo \
+nostackgap:bar
Turns on noaslr and wxneeded and turns off noprotmax for the ELF
binary foo and turns on nostackgap for the ELF binary bar.
The file paths listed in ELF_FEATURES are relative to ${BUILD_WRKSRC}.
File modifications are made post-build as certain test targets may run on
the build-tree binaries.
20220127:
AUTHOR: [email protected]
PyQt modules have been merged into devel/py-qt5-pyqt.
This allows us to simplify PyQt framework and to be in adequacy with the
packages that the author of these libraries proposes, namely:
* PyQt - devel/py-qt5-pyqt
* PyQt-Charts - x11-toolkits/py-qt5-chart
* PyQt-NetworkAuth – net/py-qt5-networkauth
* PyQt-WebEngine – www/py-qt5-webengine
* SIP – devel/py-sip
* py-sip - devel/py-qt5-sip
* PyQt-builder - devel/py-qtbuilder
* Qscintilla - devel/py-qt5-qscintilla2
Ports depending on PyQt, must be declared with USE_PYQT=pyqt5 instead of
USE_PYQT=core gui svg etc.
20220117:
AUTHOR: [email protected]
Standalone USE_GL, USE_GNOME, USE_MATE, USE_PHP, USE_SDL,
USE_XORG have been deprecated for a while. For migration
purposes the framework automatically loaded the corresponding
USES={gl,gnome,mate,php,sdl,xorg} with a warning. The migration
period is now over and you must add the USES manually for USE_*
to have any effect.
20220111:
AUTHOR: [email protected]
The CPU_AND, CPU_ANDNOT, CPU_OR, and CPU_XOR macros in 14-CURRENT
and 13-STABLE after this date have been made compatible with GLIBC
conventions. Specifically, they now take 3 arguments instead of 2.
Ports can check whether the CPU_ALLOC macro is defined and then
use the 3 parameter form, e.g.:
#ifdef CPU_ALLOC
CPU_AND(dst, dst, src);
#else
CPU_AND(dst, src);
#endif
20211211:
AUTHOR: [email protected]
A new USES has been added to depend on ImageMagick.
USES=magick
adds a LIB_DEPENDS on graphics/ImageMagick${IMAGEMAGICK_DEFAULT}.
If a specific version is required, use for example
USES=magick:6 resp. USES=magick:7
If only a build, run or test is required, use for example
USES=magick:build resp. USES=magick:6,build,test
If a dependency on the nox11 flavor is required, use for example
USES=magick:nox11 resp. USES=magick:7,nox11,run,test
See magick.mk for more details on the available flags.
20211122:
AUTHOR: [email protected]
The default compression for INDEX file as fetch via make fetchindex has
switched from .bz2 to .xz (.zst is also available).
The .bz2 format is still available but is considered deprecated and may
be removed in the future.
20211010:
AUTHOR: [email protected]
INSTALLS_ICONS has been replace by a trigger on gtk-update-icon-cache.
the macro does nothing anymore.
20211010:
AUTHOR: [email protected]
A new USES has been added, to simplify the integration of triggers in
the ports tree.
20210801:
AUTHOR: [email protected]
WANT_OPENLDAP_SASL is removed now that OpenLDAP is always built with
SASL support.
20210730:
AUTHOR: [email protected]
A new USES has been added to depend on the mlt multimedia framework.
Ports that depend on mlt should now use USES=mlt:<version> to specify
their dependency.
At the moment the supported version is 6, but will be extended to also
allow for selection of mlt 7 shortly.
20210604:
AUTHOR: [email protected]
The prepare-commit-msg hook was enhanced to auto-fill the first line of the
commit with the category/port in case only one port was committed to.
20210525:
AUTHOR: [email protected]
PYTHON_REL has been switched from a 4 digits number to a 5 digits number to
handle python 3.10.0. Ports checking for python 3.7.10 should compare
PYTHON_REL against 30710 and ports checking for python 3.10.0 should compare
PYTHON_REL against 31000.
20210420:
AUTHOR: [email protected]
A prepare-commit-msg hook was added to the repository. This hooks prepares
the commit message template for specific ports tree usage.
To make use of it, the easiest way is to run:
git config --add core.hooksPath .hooks
20201120:
AUTHOR: [email protected]
New default version for librsvg2.
Current versions of graphics/librsvg2 are using parts written in rust.
For architectures that do not have support for rust, and for people
who prefer not to have, or are not able to compile rust software due
to hardware limitations, the version can be chosen via this new flag.
The default on almost all architectures is rust.
If you prefer no to use rust, add the following to your make.conf:
DEFAULT_VERSIONS+=librsvg2=legacy
20210327:
AUTHOR: [email protected]
New @touch keyword
Its purpose is to ensure that a file is being created at install time
while not necessary tracked by the package.
20201120:
AUTHOR: [email protected]
New virtual category: education.
This category comprises ports that are mainly educational in nature or
purpose, such as:
* course-writing or course-delivery applications,
* classroom or school management applications (eg, scheduling classes),
* applications, utilities, or games primarily or substantially designed
to help the user learn a specific topic or study in general, like typing
tutors, flashcard applications, or educational games.
20201110:
AUTHOR: [email protected]
Patents are a complicated topic, and their regulation varies depending on
jurisdiction. Patents are not necessarily related to the license and so
should not be connected to the license framework.
Patent limitations within the ports tree have been removed and left to the
user or consumer to deal with their local legislation to determine if they
can use the software without legal restrictions.
20201022:
AUTHOR: [email protected]
New @rmempty keyword
Its purpose is to delete empty files at deinstallation time. It is meant
to be used for generated files/untracked by the package manager files.
It respects rootdir
20201022:
AUTHOR: [email protected]
@shell has been rewritten in lua
It provides the exact same feature set as the previous version but it is now
sandboxed and rootdir compliant (see the pkg -r option).
20201001:
AUTHOR: [email protected]
The @sample keyword was rewritten in lua.
It behaves exactly like the previous one but it is sandboxed and
is rootdir compliant (see pkg -r option).
20201001:
AUTHOR: [email protected]
packages scripts and keywords can both be written in lua (version 5.3), see
pkg-lua-script(5) for the API.
Note that all scripts written in lua will:
- run inside a capsicum sandbox,
- be rootdir compatible (see pkg -r option)
- be cross installation compatible example: installing packages in an arm64
rootdir on and amd64 host.
20200531:
AUTHOR: [email protected]
pyqt.mk gained support for test-only dependencies. If a component, say
py-qt5-gui is only required for testing, you can add
USE_PYQT=<other_deps> gui_test
20200514:
AUTHOR: [email protected]
Add PATCH_CONTINUE_ON_FAIL to allow patching to go through all the patches
even if one fail.
This helps when upgrading ports with a large number of patches, like
www/chromium where having to fix one patch, re-do the patching, fix the
fallout, 800 times, is really painful.
20200414:
AUTHOR: [email protected]
package scripts can now be done in lua, the following are supported:
- pkg-pre-install.lua
- pkg-post-install.lua
- pkg-pre-deinstall.lua
- pkg-post-deinstall.lua
see pkg-lua-script(5) for more details.
20200414:
AUTHOR: [email protected]
USES=lua gained flavors.
Ports using USES=lua:module or lua:flavors will be flavored. A range of
supported lua versions can be set using XX-YY (or XX-, or -YY, or simply ZZ)
for ports not supporting all lua versions.
USES=lua sets LUA_FLAVOR that needs to be used on all dependencies of
flavored lua ports, in a similar way as PHP or Python flavors.
20200115:
AUTHOR: [email protected]
${PREFIX}/share/man is now a valid location for manpages ${PREFIX}/man being
considered as deprecated.
20191009:
AUTHOR: [email protected]
The ipv6 virtual category is gone, it does not make sense anymore in 2019
where the norm in applications is to have support both ipv4 and ipv6.
20191001:
AUTHOR: [email protected]
BINARY_WRAPPERS allow to push in front of the PATH wrappers for binaries.
This is useful when 2 tools do provide the same feature, but the configure
scripts do test for some variables which are not in one of the tool.
20190919:
AUTHOR: [email protected]
USES=xfce now defaults to gtk3, so for ported applications requiring
GTK2 XFCE support USES=xfce:gtk2 should be used.
20190903:
AUTHOR: [email protected]
The ports tree now supports overlays
overlays are a way to help users to integrate their own ports tree
with the official ports tree without having to maintain clone of the
official tree and remerge on regular basis.
The ports tree will lookup in the overlays (in the order the are listed in
OVERLAY variable) for the dependencies and the USES. It will use the first
found.
in order to use it the user have to declare his overlays that way in their
make.conf:
OVERLAYS= overlay1 overlay2 overlay3
20181225:
AUTHOR: [email protected]
cmake.mk now defaults to out-of-sourcetree builds. The option 'outsource'
has been removed. Ports that need an intree build now can pass 'insource'.
20181110:
AUTHOR: [email protected]
texinfo files are now installed in ${PREFIX}/share/info
20180630:
AUTHOR: [email protected]
bsd.qt.mk has been replaced by qt.mk. This changes the way ports have to
depend on Qt slightly.
Previously one would have written
USE_QT4=foo bar
or
USE_QT5=foo bar
while now one has to write
USES=qt:4
USE_QT=foo bar
respectively
USES=qt:5
USE_QT=foo bar
Further qmake.mk no longer respects QT_NONSTANDARD. Ports that don't want to
get the configure environment provided by qmake.mk should add the argument
no_env, ports that don't want the configure target should specify no_configure.
20180506:
AUTHOR: [email protected]
All USE_ and WANT_ variables for PHP have been removed and marked
UNSUPPORTED. Use USES= php:<feature> as a replacement.
USE_PHPIZE, USE_PHPEXT, USE_ZENDEXT, USE_PHP_BUILD,
WANT_PHP_CLI, WANT_PHP_CGI, WANT_PHP_MOD, WANT_PHP_WEB, WANT_PHP_EMB
20180311:
AUTHOR: [email protected]
USE_APACHE has been replaced by USES=apache.
20180308:
AUTHOR: [email protected]
Ports using USES=php:phpize, php:ext, php:zend, and php:pecl are now
flavored. They will automatically get flavors (php56, php70, php71, php72)
depending of the versions they support (set with IGNORE_WITH_PHP). As a
consequence, ports using USES=pear and USES=horde are also flavored.
As all packages must have different package names, the following variables
must be used in PKGNAMEPREFIX/SUFFIX:
Variable + Values +
--------------------------------------------------------------------------------------
PHP_PKGNAMEPREFIX | php56- php72- | PHP Extensions
| | and modules
--------------------------------------------------------------------------------------
PHP_PKGNAMESUFFIX | -php56 -php72 | PHP Applications
--------------------------------------------------------------------------------------
PECL_PKGNAMEPREFIX | php56-pecl- | PECL extensions
| | automatic
--------------------------------------------------------------------------------------
PEAR_PKGNAMEPREFIX | php56-pear- | PEAR modules
| | without PEAR_CHANNEL
PEAR_<channel>_PKGNAMEPREFIX | php56-pear-channel- | with PEAR_CHANNEL
| | automatic
In all the ports with PHP dependencies, the *_DEPENDS entries MUST end with
the flavor so that the framework knows which to build/use. This is done by
appending '@${PHP_FLAVOR}' after the origin. For example:
RUN_DEPENDS= ${PEAR_PKGNAMEPREFIX}Validate>=0.5.0:devel/pear-Validate@${PHP_FLAVOR} \
${PECL_PKGNAMEPREFIX}smbclient>=0.8.0:net/pecl-smbclient@${PHP_FLAVOR} \
PHP applications (for example, www/wordpress) can also get flavors, add the
flavors keyword to USES=php, for example: USES=php:flavors, and add
${PHP_PKGNAMESUFFIX} to its PKGNAMESUFFIX.
20180125:
AUTHOR: [email protected]
Add support to passing directories to EXTRA_PATCHES.
Instead of:
EXTRA_PATCHES= ${PATCHDIR}/feat-foo-patch-file.c \
${PATCHDIR}/feat-foo-patch-file.h \
${PATCHDIR}/feat-foo-patch-file2.c
Move those files to ${PATCHDIR}/feat-foo/, name them patch-*, and set:
EXTRA_PATCHES= ${PATCHDIR}/feat-foo
20180116:
AUTHOR: [email protected]
The deprecated PYTHON_DEFAULT_VERSION, PYTHON2_DEFAULT_VERSION, and
PYTHON3_DEFAULT_VERSION have been removed.
20180106:
AUTHOR: [email protected]
USES=qmake now accepts a new variable, QMAKE_CONFIGURE_ARGS.
Starting with Qt 5.8.0, qmake can use configure.json files to help define
configuration options and configuration time checks. These options are
generally in the form '-foo -no-bar', and must be passed after "--" at the
end of qmake's command line.
The QMAKE_CONFIGURE_ARGS variable allows one to set those options, and
USES=qmake takes care of passing them at the right position when invoking
qmake.
20180102:
AUTHOR: [email protected]
There is a new USES=eigen to depend on math/eigen[23].
Usage:
USES=eigen:<version>[,<type>]
version: 2 or 3 (required)
type: build (default), run
For example:
USES=eigen:2,build,run
will add a BUILD- and RUN_DEPENDS on math/eigen2, and
USES=eigen:3
will add a BUILD_DEPENDS on math/eigen3.
20171231:
AUTHOR: [email protected]
USES=cmake now supports two additional list variables:
* CMAKE_ON : List of variables to turn on
* CMAKE_OFF : List of variables to turn off
This can be used as a shortcut to append these to CMAKE_ARGS.
For example ports that previously set
CMAKE_ARGS= -DVAR1:BOOL=TRUE -DVAR2:BOOL=TRUE -DVAR3:BOOL=FALSE
can now set this as
CMAKE_ON= VAR1 VAR2
CMAKE_OFF= VAR3
20171130:
AUTHOR: [email protected]
Ports using USE_PYTHON=distutils are now flavored. They will automatically
get flavors (py27, py34, py35, py36) depending on what versions they support.
There is also a USE_PYTHON=flavors for ports that do not use distutils but
need FLAVORS to be set. A USE_PYTHON=noflavors can be set if the port is
using distutils but flavors are not wanted.
A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been added
to cope with Python ports that did not have the Python PKGNAMEPREFIX but are
flavored.
USES=python now also exports a PY_FLAVOR variable that contains the current
python flavor. It can be used in dependency lines when the port itself is
not python flavored, for example, deskutils/calibre.
By default it will only generate flavors for the versions in PYTHON2_DEFAULT
and PYTHON3_DEFAULT. Define BUILD_ALL_PYTHON_FLAVORS in your make.conf to
generate all possible flavors. A port can set USE_PYTHON=allflavors to have
all the flavors and not simply the default ones.
In all the ports with Python dependencies, the *_DEPENDS entries MUST end
with the flavor so that the framework knows which to build/use. This is done
by appending '@${PY_FLAVOR}' after the origin. For example:
RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}six>0:devel/py-six@${PY_FLAVOR}
20171130:
AUTHOR: [email protected]
To help with flavored ports, helpers are available. In these, replace <*>
with the flavor name.
*_PKGNAMEPREFIX *_PKGNAMESUFFIX *_PLIST *_DESCR will overwrite the variable.
*_CONFLICTS *_CONFLICTS_BUILD *_CONFLICTS_INSTALL *_PKG_DEPENDS
*_EXTRACT_DEPENDS *_PATCH_DEPENDS *_FETCH_DEPENDS *_BUILD_DEPENDS
*_LIB_DEPENDS *_RUN_DEPENDS *_TEST_DEPENDS will append to the variable.
For example:
flavor2_PKGNAMESUFFIX= -foo
can replace:
.if ${FLAVOR:U} == flavor2
PKGNAMESUFFIX= -foo
.endif
20171130:
AUTHOR: [email protected]
Flavors are a way to have multiple variations of a port. The port is built
multiple times, with the variations. To declare flavors, set the FLAVORS
variable to the flavors you want defined. The first flavor will be the
default:
FLAVORS= flavor1 flavor2
The flavors MUST be lowercase, and can contain [[:lower:][:digit:]_].
Then, when building the port, pass the FLAVOR as an argument after make to
select the flavor.
$ make install FLAVOR=flavor2
In the port, you can then change the behavior depending on the value of the
FLAVOR variable. Note that the different flavors MUST have different
PKGNAMEs. Be sure to guard against an empty FLAVOR variable by using
${FLAVOR:U}:
.if ${FLAVOR:U} == flavor2
PKGNAMESUFFIX= -foo
OPTIONS_DEFAULT+= FOO
.endif
A tools guide is available at:
https://wiki.freebsd.org/Ports/FlavorsTools
A port migration guide is available at:
https://wiki.freebsd.org/Ports/FlavorsMigration
20171020:
AUTHOR: [email protected]
The USES=fmake has been removed. It was created to help migration from
old FreeBSD make (pmake) and there are no more users of it left in
the ports tree.
20171012:
AUTHOR: [email protected]
Remove WANT_GNOME and HAVE_GNOME, they were in disuse, and made useless by
options.
20171011:
AUTHOR: [email protected]
New BINARY_ALIAS variable has been added, when defined it will create symlinks
of some given binaries in a directory which will be prepended to the PATH.
The syntax is the following:
BINARY_ALIAS= target1=source1 target2=source2
For example to have a "swig" binary in the path which will be pointing at
swig3.0 and a "sed" pointing at GNU sed: gsed
BINARY_ALIAS= swig=swig3.0 sed=gsed
20170625:
AUTHOR: [email protected]
The default generator for USES=cmake ports has been switched to ninja.
Previously it was possible to opt-in to using ninja instead of make(1)
by setting CMAKE_NINJA, now ports need to opt-out.
Ports that do not build with ninja must switch from
USES=cmake:<args>
to
USES=cmake:<args>,noninja
20170417:
AUTHOR: [email protected]
New USES: meson, to handle properly the meson building system.
20170313:
AUTHOR: [email protected]
HTTPS certificates are now verified when "make makesum" fetches distfiles.
If this fails make sure you have a CA certificate bundle installed such as
security/ca_root_nss. If it still fails and there are other HTTPS sites
with a valid certificate consider removing the site from MASTER_SITES.
If the site cannot be removed you can disable certificate verification by
adding the following line to the port Makefile:
FETCH_ENV= SSL_NO_VERIFY_PEER=1 SSL_NO_VERIFY_HOSTNAME=1
20170218:
AUTHOR: [email protected]
* Qt 4's binaries have been moved to lib/qt4/bin to match what is already done
to Qt 5's binaries. Since these binaries are no longer in ${LOCALBASE}/bin,
they also do not have the -qt4 suffix in their names any more.
* Consequently, there are no Qt 4 or Qt 5 binaries in the default $PATH, and
misc/qtchooser is now used to select the actual Qt binaries. In other
words, calling "qmake" or "moc" now goes through qtchooser, which prefers
Qt 5 binaries by default.
The ports framework handles this automatically. The UPDATING entry covers
this in more detail.
* Qt 5.7.1 requires a C++11-capable compiler to be used. qmake and CMake pass
the appropriate flags to the compiler (such as -std=c++11) automatically,