On 06/05/21 18:32, Jan Beich wrote:
> Did you try CARGO_GIT_SUBDIR? See
> https://cgit.freebsd.org/ports/commit/?id=ab415159b8b9
> If that commit message is still unclear check existing consumers:
Thanks, it worked! I wasn't aware of it.
On 07/10/19 09:41, Alex Dupre wrote:
>> Some projects (e.g., Servo, Veloren) bundle several packages together.
>> When dependencies also bundle packages it confuses "git" override.
>> Any tips/workarounds that scale beyond 1 port?
>
> I haven't a soluti
ally supported by roundcube, it may
work but not 100% guaranteed
2) MySQL 8: it includes a change in the default authentication system
that broke almost all php installations. To restore the old behavior a
possibility is to use a my.cnf file with:
[mysqld]
default_authentication_plugin = mysql_
Mason Loring Bliss wrote:
> Hey all. I want to have Poudriere build packages that build and install to
> /opt instead of /usr/local.
I think you should use:
PREFIX=/opt
LOCALBASE=/opt
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
have the same issue with the
parity ethereum client (that in fact it's not in the ports tree yet).
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any ma
Alex Dupre ha scritto:
The new version of snappy/java however seems to use an sbt build,
which is quite
different. Has anyone got any experience of porting anything with an
sbt build.
Another thing you can try:
https://github.com/sbt/sbt-export-repo
--
Alex Dupre
-Dependency-Locking
--
Alex Dupre
___
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"
' will
just get me 5.4.38, not 5.6.
Correct.
So should I install lang/php56 myself now,
If you like.
or is it expected that lang/php5
will eventually become 5.6 and I should just wait,
No.
or what?
You may also stay with php 5.4, it's
Sascha A. Borer ha scritto:
> In the FreeBSD Port php55 I try to activate the extension intl.so
> Strangely, after compiling, there is no intl.so or php_intl.so available.
Simply install devel/pecl-intl
--
Alex Dupre
___
freebsd-ports@freeb
_IGNORE= yes
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
if there aren't strong
reasons to do otherwise (e.g. a highly customized bundled version)
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "fre
e cgi version. So
there isn't any problem with tinderbox/poudriere.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
y bsd.database.mk.
Exactly.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Guido Falsi ha scritto:
> I agree, but there is a consistency problem, different systems WILL
> behave differently, for a good reason though :)
I'd add that currently if you are using ports instead of packages is
because you WANT a different behavior ;-)
--
s have different needs.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Sean Bruno ha scritto:
> This seems like a broken "feature" of ports IMO. I.e. non-consistent
> runs.
It seems quite strange to me, poudriere shouldn't exhibits such behavior.
--
Alex Dupre
___
freebsd-ports@freebsd.
, so gcc48 is not found
when building other ports that doesn't strictly require it.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
ome across
'composer'. It's a dependency manager, I have no plans to support it,
you can ignore it for the moment.
- --
Alex Dupre
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (FreeBSD)
Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/
iEYEARECAAYFAlONwxgA
Koichiro IWAO ha scritto:
> archivers/rpm fails to build around aclocal macro.
Same issue yesterday, today it builds fine.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscr
"")
+USE_APACHE=22+
+.include "${PORTSDIR}/Mk/bsd.apache.mk"
RUN_DEPENDS+=
${PHPBASE}/${APACHEMODDIR}/libphp5.so:${PORTSDIR}/${MOD_PHP_PORT}
.endif
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/m
e problem with hplip installing
cups-filter: I don't know which one is the correct way.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
l php stuff without option ZTS enabled to
> get rid of the wrong path, but it seems I didn't hit the culprit
> port.
You did exactly the opposite of what you had to do. As the WARNING
says, build lang/php5 with ZTS enabled and rebuild all extensions.
- --
Alex Dupre
-BEGIN PGP SIGNAT
Koichiro IWAO ha scritto:
> java/linux-sun-jdk18 was added just now but isn't it identical to
> java/linux-oracle-jdk18 ? Why -sun- port is needed?
It was removed 30 minutes after the commit :-)
--
Alex Dupre
___
freebsd-ports@freebsd.org m
/HP_LaserJet_M1522nf_MFP) from localhost
> Something that I think needs to be brought up. It appears that since
> CUPS 1.6.x, cups-filters is required for it to work with most printers.
I confirm that installing cups-filters restored correct behavior f
cannot be used on a
> section.
ProxyPassMatch Directive
Context:server config, virtual host, directory
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send a
Greg Rivers ha scritto:
> The recent update from mysql56-client-5.6.15 to mysql56-client-5.6.16
> fails to build on 9.2-STABLE i386. It builds fine on amd64 (both
> 9.2-STABLE and 10.0-STABLE).
Unable to reproduce, it builds fine also on my 9.2-i386 poudriere jail.
--
A
ing is broken in the ports tree.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Baptiste Daroussin ha scritto:
> It is since pkg 1.2.2
Ops, sorry for the noise, I checked on a machine with an older 'pkg'.
- --
Alex Dupre
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (FreeBSD)
Comment: Using GnuPG with Sea
sets the chmod file, @owner the user and
>> such.
>>
>
> man pkg-create or man pkg_create
I cannot find anything in 'man pkg-create' about such keywords. They
were explained in 'man pkg_create' but it's not installed anymore on
newer FreeBSD releases.
- -
Thierry Thomas ha scritto:
> How should we stagify ports writing out of their $PREFIX for
> good reasons, e.g. a statedir like /var/foo/$PORTNAME.
Usually such directories are created at runtime (perhaps by the startup
rc script) and not during package installation.
--
Alex
tional info or this second one is enough.
- --
Alex Dupre
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.21 (FreeBSD)
Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/
iEYEARECAAYFAlJNMdAACgkQgRXp2M5fVU11iQCgmj+i9/UUJDKP1mdgAzAMYbO2
MD8AnRbMZ3rQr+K9SSyXDFgPg1JsvHrc
=KChF
---
t as of
> yesterday)
I think the issue was that such very first email was lost somewhere,
as Stefan said there isn't in the mailing list archive, I've never
received originally, but there a few replies to it. Can you resend it
to the list, please?
- --
Alex Dupre
-BEGIN PGP SIGN
10 types of people in the world: who want php port always
updated to the latest branch and who want a new set of phpXX ports for
every branch.
It's impossible to satisfy both types, unless we keep an additional set
of 'php' ports with the same contents of latest &
Subbsd ha scritto:
> So, www/pecl-zendopcache is still necessary for lang/php55 when we need
> for zend opcode? Thanks
You should use pecl-zendopcache for now, they are the same extension.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing lis
Andrea Venturoli ha scritto:
> Perhaps I picked it up in some unobvious way... or perhaps should it be
> added as a dependency?
Fixed, added as dependency, thanks for reporting.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing lis
e removed / moved to lang/php54.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
ment. Are there any better examples?
Basically there are two types of implementation with different pro/cons:
profiles and symlinks.
vboxheadless is in the first category, tomcat7 in the second one:
http://svnweb.freebsd.org/ports/head/www/tomcat7/files/tomcat7.in?revision=307489&
them, not show the popup
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
a changed option but only when the user explicitly type make config?
Just a proposal, please give your opinion.
I find such behavior very useful, I find annoying the above behavior. If
the dialog will not pop-up if the only options are the global ones it'd
be much better, IMO.
--
Alex
reeBSD.
> However, this would still exclude cleanroom package building
> environments like poudriere or tinderbox, correct?
Just fixed, now it always build a ssl-enabled php5-ftp without requiring
php5-openssl.
--
Alex Dupre
___
freebsd-ports
Alex Dupre ha scritto:
> Said so, such behavior should be harmonized, probably you could get a
> ssl-enabled php5-ftp even without php5-openssl. I'll work on a patch.
After checking, I saw that it was already so in the past. A recent
update broke it, but I've just fixed it. You do
very simple way: build
php5-ftp after php5-openssl.
Said so, such behavior should be harmonized, probably you could get a
ssl-enabled php5-ftp even without php5-openssl. I'll work on a patch.
--
Alex Dupre
___
freebsd-ports@freebsd.org maili
{APXS} -q MPM_NAME
-. if ${APACHE_MPM} == "worker" || ${APACHE_MPM} == "event"
+APACHE_THR!=${HTTPD} -V | ${GREP} threaded
+. if ${APACHE_THR:Myes}
PHP_EXT_DIR:= ${PHP_EXT_DIR}-zts
. endif
.elif defined(APACHE_PORT) && (${APACHE_PORT:M*worker*} != &
doing what the Porters Handbook suggested, and it just
> bombs out with this useless message:
You should add:
.include
before checking for ${PORT_OPTIONS:MDOCS}
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org
l permission, but if it's
listed in LEGAL it should be marked as RESTRICTED or NO_CDROM, otherwise
it should not listed there (the LICENSE framework already says that
special authorization has been granted).
--
Alex Dupre
___
freebsd-ports
I'd say this is enough for
generating LEGAL (modulo correct use of these knobs).
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
.
For particular licenses we already have a controversial LICENSE framework.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
sons.
For license reasons we already have this:
# RESTRICTED- Prevent the distribution of distfiles and packages to
# the FTP sites or on CDROM (e.g.
forbidden by license
# considerations).
and re
t it doesn't work for my FreeBSD-8.0.
> The gcc-4.2 from base (under name 'cc') is used anyway with the same error
The patch was actually committed to the FreeBSD ports tree only recently
(18 hours ago). Are you sure you have it?
--
Alex Dupre
__
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florian Smeets wrote:
> Jan committed a patch that should work, is that an acceptable
> workaround for your use case (it pulls in a newer gcc)? Can you
> test it and report back?
Yes, it works correctly, thanks.
- --
Alex Dupre
-
27;ll work on a patch tomorrow. I think the patch should simply
disable building INTEL_GCM on FreeBSD < 8.3, correct?
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florian Smeets wrote:
> It works fine on anything >= 8.3.
Packages are usually built on N.0 releases and in fact my tinderbox
with 8.2-RELEASE fails with:
cc1: error: unrecognized command line option "-mssse3"
- --
Alex Dupr
DIR)/$(PROG_PREFIX)intel-gcm$(OBJ_SUFFIX): ASFLAGS +=
- -no-integrated-as
endif
endif
It requires -mssse3 flag, so it cannot be built on 8.x with base gcc:
cc1: error: unrecognized command line option "-mssse3"
It uses assembly code not recognized by clang.
I'd say we should
Domas ha scritto:
Is there any time frame known when MySQL 5.6 port will be available ?
Nope, I'm working on it, but no ETA.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-por
/eclipse-ecj port?
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
:
# client).
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
#x27;t it be placed somewhere like /usr/local/etc ?
The reason is exactly the same as before, but yes, in this particular
case it may not be the best decision (probably not installing it at all
would be better).
--
Alex Dupre
___
freebsd-ports@freebsd.
? The MySQL 5.5
ports are so for a reason. From the original commit log:
- new installation layout, resembling RPM packages:
- client = Client Utilities + Development Libraries + Shared components
- server = MySQL Server + Embedded
--
Alex
Alexandr Kovalenko ha scritto:
At least it should be installed with server package, not client.
It is installed together with headers needed to build plugins.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman
Alexandr Kovalenko ha scritto:
Fixed pkg-plist bug with libmysqlservices.a (which, btw, should be
fixed in mysql55-client too - libmysqlservices.a should not be
installed in any of packages).
Why do you say so? libmysqlservices.a is needed to create plugins.
--
Alex Dupre
obviously.
>> (from the [current:revision:age] version = current - age rule)
>
> This should be mandatory knowledge for every ports committer.
Yes, it should. It's explained here:
http://www.freebsd.org/gnome/docs/gnome_porting.html
Not much visible or clear that it's not limited to
say that when there are shared library
bumps the commits should be checked and reviewed by multiple eyes.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
ersion, [3:0:2])
+m4_define(libpcre16_version, [2:0:2])
It says that the new shared lib is compatible with the old lib (only new
interfaces were added), since:
1 - 0 = 3 - 2 = 1
1 - 0 = 2 - 2 = 0
(from the [current:revision:age] version = current - age rule)
es?
>
> sysutils/libchk or pkg_libchk from sysutils/bsdadminscripts.
Uh? One of the two:
1) it keeps all versions and you need to clean them up
2) it keeps only needed and so you shouldn't clean up
The correct answer is 1)
--
Alex Dupre
___
freeb
round until we make
delete-old-libs. Why should ports be different?
Also for src the policy is: don't recompile any ports after an upgrade,
or recompile them all, exactly for this reason.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing li
Jeremy Messenger ha scritto:
>> Absolutely yes from me. The -w option is real lifesaver and should be
>> on by default.
>
> I disagree. The -w is a temp fix and not a correct solution, so it
> shouldn't be default.
I agree with your disagr
+-+
Taking - it has a shlib bump, so will wait for port freeze to be done.
Sure? shlib bump between 4.0.0 and 4.0.1 seems quite strange to me.
Probably using:
USE_GNOME= ltverhack
USE_AUTOTOOLS= libtool
will fix shlib numbering.
--
Alex Dupre
ct the LATE_(UN)SET parameter can be used inside the port
> after including bsd.port.options.mk (where I really miss it) and CMD_(UN)SET
> from the command line.
Hmm, no, I've understood that they are simply two different proposals
for the same features, i.e. command line overrid
needed to build the port.
And you shouldn't put if after inclusion of bsd.port.pre.mk.
RUN_DEPENDS is for things required at runtime and so usually installed
in the install step.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http:
rt bootstrapping in 10 seconds. Press CTRL-C now to abort"
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
If you are interested in eaccelerator with php 5.4, please try the
following patch and report success/failure.
http://www.alexdupre.com/eaccelerator.diff
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman
bjection was ignored.
If you can feel better, I never approved it.
> OTOH, the recent enigmail update worked for me using portmaster, I
> haven't had time to investigate why it worked this time either. :)
Because I put that horrible FETCH_DEPENDS inside a conditio
re they acceptable? Are this problem known also on other
> systems/architectures?
They are partially correct (removing the offending 'case' is not
correct). I have additional patches to also fix build with kde4 that are
running on my tinderbox now
Beat Gaetzi ha scritto:
> Yes, to get SeaMonkey 2.10.1 running we need to change parts of
> bsd.gecko.mk which affects other ports and this needs more testing.
Is such path available somewhere?
--
Alex Dupre
___
freebsd-ports@freebsd.org mailin
e quantis-kmod patch. I think simply removing
SRC_BASE?= line is the correct fix.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
is handled only
by a small percentage, so, if I have understood correctly, many ports
should include OPTIONS_EXCLUDE=NLS. Is it correct?
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To
Svyatoslav Lempert ha scritto:
> FreeBSD 8.3 is done, please commit update lang/php5 to PHP 5.4 to
> portstree. Thank you in advance.
I'm just waiting for final release of suhosin (both patch and extension)
to commit the update.
--
Chris Rees ha scritto:
>> On a tangential issue, php52 should probably be kept around, at least for
>> now.
>
> The PHP maintainer disagreed on this point last week-ish.
Eh?! I never said it. It' fine to keep a maintained (not by me) php52,
since php5 will be updated t
you prefer?
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
e updated to this
release before switching to (probably) 5.4.1.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
t up your own tinderbox or package builder machine.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
maintainer and a committer willing to create and maintain lang/php53.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
BTOOLFILES to include all the 'configure'
scripts.
In any case, a bump will be necessary, because the shared version number
will decrease, but at least it won't be necessary next times.
--
Alex Dupre
___
freebsd-ports@freebsd.org mai
d 'age' ? If only a new interface has been added, age should be
incremented too, and so the shared library bump is not needed. If so,
you can use:
USE_AUTOTOOLS= libtool
USE_GNOME= ltverhack
to avoid bumping.
--
Alex Dupre
___
freebs
Matthew Seaman wrote:
Adding code to run ldd(1)
against the files installed by the port and processing the results
shouldn't be too hard.
This could be an idea for ports maintainers, to verify if LIB_DEPENDS is
set correctly, but cannot be used as its generic replacement.
--
Alex
opposite case: ports that have direct
(maybe not needed) dependencies to libraries that are not recorded in
Makefiles. This is the root cause of "portmaster -r" or aggressive bumps.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
h
Alex Dupre wrote:
And consequentially it should be bumped *only if* a direct dependency
has a library version bump.
This doesn't solve the fact that in 3 days my tinderbox has rebuilt
nearly all ports 4 times. Is there a way to say tinderbox to not rebuild
every ports (without portrev
Alex Dupre wrote:
Ideally a port should include in LIB_DEPENDS all the direct dependencies.
And consequentially it should be bumped *only if* a direct dependency
has a library version bump. With the current "link to all" attitude, we
are never sure what need to be bumped, because
experiment seriously with ${EXPLICIT_PACKAGE_DEPENDS} and
libtool patch to not link to indirect dependencies (ports/104877).
Ideally a port should include in LIB_DEPENDS all the direct dependencies.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing
Martin Wilke wrote:
I facing since a while on all my servers that mysql 5.5.20 fails to build. Have
anyone of you seen something like that,
Nope, sorry.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman
Steven Hartland wrote:
I suspect the change meant to add this additional fix to the Makefile
patch but instead replaced it.
Damn, yes, right.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
27;ll have to ask ale@ about php.
Well, I'd say the only error about php is the default version, that's
not 4 anymore, but 5.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
thers?
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Doug Barton ha scritto:
# Default: ${PREFIX}/www/${PORTNAME}
I went with ${WWWDIR} in the Makefile/plist so hopefully that will
future-proof it in the event of a change.
Yup, I meant WWWDIR with www/appname.
--
Alex Dupre
Doug Barton wrote:
I'm also curious about the advice to install stuff into
/usr/local/www/appname. I vaguely remember that this was deprecated but
it seems to still be true.
I'm not aware of any deprecation, all my webapp ports install into
www/appname.
--
self to do it
for all the ports depending on libungif a few weeks ago ;-)
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Doug Barton ha scritto:
Other than the mismatched checksums I haven't noticed any actual
problems, so this is more of an "Is this a problem?" question.
AFAIK all ports should switch to giflib and libungif should be removed
from the tree.
Marco Steinbach ha scritto:
shouldn't I be able to fetch distfiles for conflicting ports, if
DISABLE_CONFLICTS is set ?
Yes, but in this case you should also set -DNO_IGNORE
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Boris Samorodov ha scritto:
The problem is: while start-up zoneminder is launched after mysql
was started but is not responding yet.
Actually this should not happen. mysql rc script has a poststart
directive to wait until the daemon is up and running.
--
Alex Dupre
1 - 100 of 312 matches
Mail list logo