| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
* lose the bison175 port, it's not needed for now and will
only confuse matters
* clean up devel/Makefile, modules, and MOVED appropriately
* take maintainership of the bison* ports
Approved by: portmgr
|
| |
|
|
|
|
| |
after 5.4-RELEASE.
|
|
|
|
| |
Ports Collection documentation and use 'ARCH' rather than 'MACHINE_ARCH'.
|
|
|
|
| |
remaining non-system directories in case they're still in use.
|
| |
|
|
|
|
|
| |
PR: ports/74189
Submitted by: maho
|
|
|
|
|
|
|
| |
to GNU for inclusion in the main tree.
PR: ports/74436
Submitted by: Uranus uranus - a t - it dot muds dot net
|
|
|
|
|
|
|
|
|
|
| |
- add WITHOUT_NLS for USE_GETTEXT
- utilize INFO
- replace LOCALBASE with PREFIX
PR: 72646
Submitted by: leeym
Approved by: maintainer timeout
|
|
|
|
| |
Pointy hat to: leeym
|
| |
|
| |
|
|
|
|
|
| |
Submitted by: trevor
Tested by: bento
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
that way ports that require bison1875 (ie: PostgreSQL 7.4+) can properly
detect this dependency. Given both bison's have the appropriate CONFLICTS
sections, this should be a big enough hint to users to move from
bison < 1.875 to something more recent. Bump port revision.
Pointy hat to: bison(1) authors for grammar incompatibilities
|
|
|
|
|
| |
PR: ports/56242
Submitted by: Thierry Thomas <thierry@pompo.net>
|
|
|
|
| |
Prodded by: kris
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
PostgreSQL), however the new bison also breaks many many ports. Compromise
with a new port. Installs as bison and _not_ bison1875 and should be
mutually exclusive to the main bison port. Hopefully the bison authors will
clean up their product and this port can disappear when the base bison port
is updated in the future or enough ports are updated to work with newer
versions of bison.
Repo copied by: fjoe
Approved by: kris
|
| |
|
|
|
|
|
| |
Approved by: kris
Discussed on ports
|
|
|
|
|
|
|
|
| |
is better studied
o Turn PORTCOMMENT variable in Makefile back into pkg-comment files
Approved by: kris (portmgr hat),
portmgr, re (silence)
|
|
|
|
| |
Approved by: pat
|
| |
|
| |
|
|
|
|
|
| |
PR: 44223
Submitted by: tkato@prontomail.com
|
|
|
|
|
|
|
|
|
|
| |
list by bsd.port.mk insert anti foot-shooting device, which prevents
infinite fork loop when the user defines corresponding USE_XXX in global
make.conf, command line or environment.
Similar devices should probably be inserted into ports that might be inserted
into dependency list by others bsd.foo.mk files (bsd.ruby.mk, bsd.python.mk
and so on.)
|
|
|
|
| |
PORTREVISION.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
libiconv.
|
| |
|
|
|
|
| |
triggering an auto* build cascade.
|
| |
|
|
|
|
|
|
| |
XXX Explicitly build with included libintl for now.
PR: 35653
|
| |
|
| |
|
|
|
|
|
|
|
| |
This version was tested locally by a few trusted committers & friends,
and is believed to *actually* be as usable and stable as version 1.28.
(unlike *cough*, *cough* other 1.3x versions which have caused no end
of problems...)
|
|
|
|
|
|
| |
Back out the downgrade, I would have never agreed to it if I had know...
This leaves a window of downgradededness 18 hours -- people can just live
with that.
|
| |
|
|
|
|
|
| |
do some regression tests on their later releases.
Versions 1.29 and 1.30 seg fault where 1.28 did not.
|
|
|
|
| |
different semantics than our bsd.port.mk provides.
|
|
|
|
|
| |
Version 1.29 had several problems that I believe 1.30 fixes (looking at the
ChangeLog).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Added `-g' and `--graph'.
* Added `--locations' and `%locations'.
* Added `-S' and `--skeleton'.
* `%raw', `-r', `--raw' is disabled.
* Special characters are escaped when output. This solves the problems
* New directives.
`%yacc', `%fixed_output_files', `%defines', `%no_parser', `%verbose',
`%debug', `%source_extension' and `%header_extension'.
* The input and the output files has automatically a similar extension.
Submitted by: demon
|
| |
|
| |
|