OpenSSL 1.0.2l
Hello, The distinfo for openssl 1.0.2l seems to have the wrong paths: openssl-1.0.2l/openssl-1.0.2l.tar.gz instead of openssl-1.0.2/openssl-1.0.2l.tar.gz This applies to all the entries in distinfo. --- Horatiu ___ 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: Several PostgreSQL versions installed
On Thu, 2017-05-25 at 22:06 +0200, Baptiste Daroussin wrote:
> On Thu, May 25, 2017 at 09:59:08PM +0200, José García Juanino wrote:
> > Hi FreeBSD porters,
> >
> >
> > I have been read the following thread
> >
> > "Proposal to fix postgresql package maintainance nightmare"
> >
> > https://lists.freebsd.org/pipermail/freebsd-ports/2015-July/099842.
> > html
> >
> > but I think that, two years later, there is no progress on this
> > matter.
> > I am unaware if there is any project that addresses this issue, so
> > my
> > apologies if this work is already in progress.
>
> No progress as far as I am aware. except a PoC (early, ugly,
> unfinished)
> https://people.freebsd.org/~bapt/pgsql95.diff
>
> >
> > The goal of the new postgresql port schema should be, in my honest
> > opinion:
> >
> > * It must allow to install distinct version without ugly hacks as
> > jails,
> > etc. Jails are a overkill to accomplish this task.
> >
> > * Each software version must live in a separate directory
> > ${LOCALBASE}/pgsql/X.Y:
> >
> > /usr/local/pgsql/9.2
> > /usr/local/pgsql/9.4
> > /usr/local/pgsql/9.6
> >
> > and so on.
>
> Yes this is what I was proposing
> >
> >
> > * It is not necessary to provide an installed version as the
> > default.
> > For example, if we need 9.5 and 9.6 versions installed, both are
> > equally valid, and we do not need the standard postgresql
> > binaries
> > (pg_dump, psql, pg_ctl, etc) installed in the standard PATH as
> > /bin:/usr/bin:/usr/local/bin. Those binaries are located under
> > /usr/local/pgsql/X.Y/bin directory, and everyone can configure
> > the
> > shell environment variable PATH to add the previous directory:
> > PATH=$PATH:/usr/local/pgsql/X.Y/bin. Please do not make symlinks
> > from
> > /usr/local/bin/pg_some to specific
> > /usr/local/pgsql/X.Y/bin/pg_some,
> > it has very little advantages and a lot of drawbacks. Under a
> > prompt
> > command line, a skilled database administrator always need to
> > know
> > what command version is executing and do not need an standard
> > location
> > as /usr/local/bin.
>
> For a database administrator yes playing with the path is enough, but
> for a new
> comer installing pgsql for his blog this would be complicated
> >
> >
> > * The rc and the periodic script must be versioned also:
> >
> > /usr/local/etc/rc.d/postgresql9.6
> > /usr/local/etc/rc.d/postgresql5.6
> >
>
> yes
>
> One important thing is there is a need for a small modification for
> the
> postgresql build system: add a proper RUNPATH for the binaries to
> always find
> the right libpq
>
> >
> >
> > Best regards, and thanks to the volunteers for make FreeBSD an
> > great
> > operating system!
> >
>
> Note that the same should apply to mysql/mariadb/etc
>
And in a perfect world, PHP also. We run different versions in
different jails now. While it works, it is a bit of overkill.
--
Jim Ohlstein
Professional Mailman Hosting
https://mailman-hosting.com/
___
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: Several PostgreSQL versions installed
On Thu, May 25, 2017 at 09:59:08PM +0200, José García Juanino wrote:
> Hi FreeBSD porters,
>
>
> I have been read the following thread
>
> "Proposal to fix postgresql package maintainance nightmare"
>
> https://lists.freebsd.org/pipermail/freebsd-ports/2015-July/099842.html
>
> but I think that, two years later, there is no progress on this matter.
> I am unaware if there is any project that addresses this issue, so my
> apologies if this work is already in progress.
No progress as far as I am aware. except a PoC (early, ugly, unfinished)
https://people.freebsd.org/~bapt/pgsql95.diff
>
> The goal of the new postgresql port schema should be, in my honest
> opinion:
>
> * It must allow to install distinct version without ugly hacks as jails,
> etc. Jails are a overkill to accomplish this task.
>
> * Each software version must live in a separate directory
> ${LOCALBASE}/pgsql/X.Y:
>
> /usr/local/pgsql/9.2
> /usr/local/pgsql/9.4
> /usr/local/pgsql/9.6
>
> and so on.
Yes this is what I was proposing
>
>
> * It is not necessary to provide an installed version as the default.
> For example, if we need 9.5 and 9.6 versions installed, both are
> equally valid, and we do not need the standard postgresql binaries
> (pg_dump, psql, pg_ctl, etc) installed in the standard PATH as
> /bin:/usr/bin:/usr/local/bin. Those binaries are located under
> /usr/local/pgsql/X.Y/bin directory, and everyone can configure the
> shell environment variable PATH to add the previous directory:
> PATH=$PATH:/usr/local/pgsql/X.Y/bin. Please do not make symlinks from
> /usr/local/bin/pg_some to specific /usr/local/pgsql/X.Y/bin/pg_some,
> it has very little advantages and a lot of drawbacks. Under a prompt
> command line, a skilled database administrator always need to know
> what command version is executing and do not need an standard location
> as /usr/local/bin.
For a database administrator yes playing with the path is enough, but for a new
comer installing pgsql for his blog this would be complicated
>
>
> * The rc and the periodic script must be versioned also:
>
> /usr/local/etc/rc.d/postgresql9.6
> /usr/local/etc/rc.d/postgresql5.6
>
yes
One important thing is there is a need for a small modification for the
postgresql build system: add a proper RUNPATH for the binaries to always find
the right libpq
>
>
> Best regards, and thanks to the volunteers for make FreeBSD an great
> operating system!
>
Note that the same should apply to mysql/mariadb/etc
bapt
signature.asc
Description: PGP signature
Several PostgreSQL versions installed
Hi FreeBSD porters,
I have been read the following thread
"Proposal to fix postgresql package maintainance nightmare"
https://lists.freebsd.org/pipermail/freebsd-ports/2015-July/099842.html
but I think that, two years later, there is no progress on this matter.
I am unaware if there is any project that addresses this issue, so my
apologies if this work is already in progress.
The goal of the new postgresql port schema should be, in my honest
opinion:
* It must allow to install distinct version without ugly hacks as jails,
etc. Jails are a overkill to accomplish this task.
* Each software version must live in a separate directory
${LOCALBASE}/pgsql/X.Y:
/usr/local/pgsql/9.2
/usr/local/pgsql/9.4
/usr/local/pgsql/9.6
and so on.
* It is not necessary to provide an installed version as the default.
For example, if we need 9.5 and 9.6 versions installed, both are
equally valid, and we do not need the standard postgresql binaries
(pg_dump, psql, pg_ctl, etc) installed in the standard PATH as
/bin:/usr/bin:/usr/local/bin. Those binaries are located under
/usr/local/pgsql/X.Y/bin directory, and everyone can configure the
shell environment variable PATH to add the previous directory:
PATH=$PATH:/usr/local/pgsql/X.Y/bin. Please do not make symlinks from
/usr/local/bin/pg_some to specific /usr/local/pgsql/X.Y/bin/pg_some,
it has very little advantages and a lot of drawbacks. Under a prompt
command line, a skilled database administrator always need to know
what command version is executing and do not need an standard location
as /usr/local/bin.
* The rc and the periodic script must be versioned also:
/usr/local/etc/rc.d/postgresql9.6
/usr/local/etc/rc.d/postgresql5.6
Best regards, and thanks to the volunteers for make FreeBSD an great
operating system!
--
José G. Juanino
___
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"
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ multimedia/vdr | 1.7.29 | 2.3.5 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ 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: Recoll version bump in ports
I had short time open a update PR (Bug 219481).
Compiles fine with the port, but not with poudriere;
libtool: install: warning: `librecoll.la' has not been installed in
`/usr/local/lib/recoll'
libtool: install: install -m 555 -s .libs/recollindex
/wrkdirs/usr/ports/deskutils/recoll/work/sta
ge/usr/local/bin/recollindex
(cd python/recoll; \
if test -f /etc/debian_version ; then \
OPTSFORPYTHON=--install-layout=deb; \
fi; \
set -x; \
python setup.py install \
--prefix=/usr/local --root=${DESTDIR:-/} ${OPTSFORPYTHON})
+ python setup.py install --prefix=/usr/local
--root=/wrkdirs/usr/ports/deskutils/recoll/work/stage
python: not found
gmake[3]: *** [Makefile:2189: recollpython-install] Error 127
gmake[3]: Leaving directory
'/wrkdirs/usr/ports/deskutils/recoll/work/recoll-1.23.2'
gmake[2]: *** [Makefile:2006: install-am] Error 2
I have no clue to solve it.
so I closed the PR. I hope I or someone other could find a solution.
(Maybe, librecoll.la is the cause).
___
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: Document for OPTIONS syntax in /etc/make.conf, where to find?
On 25 May 2017 at 19:47, Thomas Mueller wrote: [...] > The new synth has no mechanism for configuring options; I guess that would > have to be done by > make config-recursive , > possibly several times until there is nothing more left to configure, as I > did when using portupgrade and later portmaster. >From synth(1) man page: -make.conf This is an optional, user-provided file. If it exists, the builder's /etc/make.conf will be appended with the contents of this file. For the default profile, the file would normally be located at /usr/local/etc/synth/LiveSystem-make.conf Cheers. -- Jonathan Chen ___ 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: Document for OPTIONS syntax in /etc/make.conf, where to find?
> > On 24 May, 2017, at 21:52, Thomas Mueller wrote: > > Where do I find documentation so I get the correct syntax for setting ports > > options in /etc/make.conf ? > > I tried "man ports", "man make", "man make.conf", and the online Porters' > > Handbook but have been unable to find the needle in the haystack. > > NetBSD pkgsrc and Gentoo (Linux) portage document this much better. > Tom > You'll find some info in the instructions at the top of > /usr/ports/Mk/bsd.options.mk; there's not a lot of info because it's not > generally the preferred place to specify options. > To turn something off by default on all ports (which can always be overridden > by make config), OPTIONS_UNSET= NLS > To turn something off which overrides make config, OPTIONS_UNSET_FORCE=NLS > You can set options for individual ports in make.conf too, though it's almost > always a better idea to run 'make config' or 'poudriere options': > /usr/ports/editors/vim$ make -V OPTIONS_NAME > editors_vim > make.conf: > editors_vim_UNSET= NLS # Adam > Adam Weinberger While the newer dialog4ports is a big improvement over the previous dialog, it is still difficult to go back in case of finger error. Previous dialog tended to make a mess of the screen, especially when I teed to a log file. Now I have a better idea what to do to set options. I still have in /etc/make.conf from some time ago, OPTIONS_SET.mpop=GNUTLS NLS I guess that would need to be revised to mail_mpop_set=GNUTLS NLS if I stay with the same options. The new synth has no mechanism for configuring options; I guess that would have to be done by make config-recursive , possibly several times until there is nothing more left to configure, as I did when using portupgrade and later portmaster. Thanks for the tips! Other options-configuring systems don't have the dialog: I am thinking of NetBSD pkgsrc and Gentoo portage (not all-inclusive). Tom ___ 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"
