| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
- Add license
Approved by: mentors (implicit)
|
|
|
|
|
| |
PR: 133318
Submitted by: Ports Fury
|
|
|
|
| |
reasonable standard.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
- Remove CONFIGURE_TARGET hack in various bsd.*.mk
- USE_GNOME=gnometarget is now an no-op
Changes to individual ports, other than removing the CONFIGURE_TARGET hack:
= pkg-plist changed (due to the ugly CONFIGURE_TARGET prefix in * executables)
- comms/gnuradio
- science/abinit
- science/elmer-fem
- science/elmer-matc
- science/elmer-meshgen2d
- science/elmerfront
- science/elmerpost
= use x86_64 as ARCH
- devel/g-wrap
= other changes
- print/magicfilter
GNU_CONFIGURE -> HAS_CONFIGURE since it's not generated by autoconf
Total # of ports modified: 1,027
Total # of ports affected: ~7,000 (set GNU_CONFIGURE to yes)
PR: 126524 (obsoletes 52917)
Submitted by: rafan
Tested on: two pointyhat 7-amd64 exp runs (by pav)
Approved by: portmgr (pav)
|
| |
|
|
|
|
|
| |
PR: 117086
Tested by: -exp runs
|
|
|
|
| |
Approved by: ahze (mentor)
|
|
|
|
|
| |
PR: ports/97030
Submitted by: Shaun Amott <shaun@inerd.com>
|
| |
|
|
|
|
|
| |
PR: ports/79974
Submitted by: Ports Fury
|
|
|
|
| |
after 5.4-RELEASE.
|
|
|
|
| |
Ports Collection documentation and use 'ARCH' rather than 'MACHINE_ARCH'.
|
| |
|
|
|
|
|
|
| |
is used.
Submitted by: Bohdan Horst <nexus@irc.pl>
|
| |
|
|
|
|
| |
(Part 2)
|
| |
|
| |
|
|
|
|
| |
Approved by: fjoe (mentor)
|
|
esmtp is a user configurable relay-only Mail Transfer Agent
(MTA) with a sendmail compatible syntax. It's based on libESMTP
supporting the AUTH (including the CRAM-MD5 and NTLM SASL
mechanisms) and the StartTLS SMTP extensions.
These are the esmtp features:
* fully sendmail command line compatible,
* supports the AUTH SMTP extension, with the CRAM-MD5 and
* NTLM SASL mechanisms,
* support the StartTLS SMTP extension,
* requires no administration privileges,
* individual user configuration,
* does not receive mail, expand aliases or manage a queue.
PR: 54491
Submitted by: Kirill Ponomarew <ponomarew@oberon.net>
|