Request for a commiter [py-lxml]

[Loïc BLOT]

Hello

I pushed the following patch to update lxml. I need it before sending
py-searx 0.14 update.

Can someone do it ?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226032

Thanks in advance
-- 
Best regards,
Loïc BLOT, 
UNIX systems, security and network engineer
http://www.unix-experience.fr

___
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"

editors/gedit-plugins

[The Doctor]

Need help  understanding why this is happening:


Script started on Mon Feb 19 20:00:38 2018
You have mail.
root@doctor:/usr/ports/editors/gedit-plugins # make

root@doctor:/usr/ports/editors/gedit-plugins # make install

===>  Installing for gedit-plugins-3.18.0
===>  Checking if gedit-plugins already installed
===>   Registering installation for gedit-plugins-3.18.0
pkg-static: Unable to access file 
/usr/ports/editors/gedit-plugins/work/stage/usr/local/lib/gedit/plugins/synctex.plugin:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/editors/gedit-plugins/work/stage/usr/local/lib/gedit/plugins/synctex/__init__.py:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/editors/gedit-plugins/work/stage/usr/local/lib/gedit/plugins/synctex/__pycache__/__init__.cpython-36.pyc:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/editors/gedit-plugins/work/stage/usr/local/lib/gedit/plugins/synctex/__pycache__/__init__.cpython-36.opt-1.pyc:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/editors/gedit-plugins/work/stage/usr/local/lib/gedit/plugins/synctex/__pycache__/evince_dbus.cpython-36.pyc:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/editors/gedit-plugins/work/stage/usr/local/lib/gedit/plugins/synctex/__pycache__/evince_dbus.cpython-36.opt-1.pyc:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/editors/gedit-plugins/work/stage/usr/local/lib/gedit/plugins/synctex/__pycache__/synctex.cpython-36.pyc:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/editors/gedit-plugins/work/stage/usr/local/lib/gedit/plugins/synctex/__pycache__/synctex.cpython-36.opt-1.pyc:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/editors/gedit-plugins/work/stage/usr/local/lib/gedit/plugins/synctex/evince_dbus.py:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/editors/gedit-plugins/work/stage/usr/local/lib/gedit/plugins/synctex/synctex.py:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/editors/gedit-plugins/work/stage/usr/local/share/appdata/gedit-synctex.metainfo.xml:No
 such file or directory
*** Error code 74

Stop.
make: stopped in /usr/ports/editors/gedit-plugins
root@doctor:/usr/ports/editors/gedit-plugins # exit

exit

Script done on Mon Feb 19 20:00:54 2018
-- 
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 on Atheism
Not by age but by capacity is wisdom acquired.  -Titus Maccius Plautus
___
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"

net/vinagre issue

[The Doctor]

Why is this happening?


Script started on Mon Feb 19 20:00:13 2018
You have mail.
root@doctor:/usr/ports/net/vinagre # make

root@doctor:/usr/ports/net/vinagre # make install

===>  Installing for vinagre-3.18.2_5
===>  Checking if vinagre already installed
===>   Registering installation for vinagre-3.18.2_5
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/C/vinagre/connect-file.page:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/C/vinagre/connect-reverse.page:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/C/vinagre/connect.page:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/C/vinagre/figures/preferences-desktop-remote-desktop.png:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/C/vinagre/figures/vinagre-connected-3-16.png:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/C/vinagre/fullscreen.page:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/C/vinagre/index.page:No 
such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/C/vinagre/introduction.page:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/C/vinagre/keyboard-shortcuts.page:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/C/vinagre/legal.xml:No 
such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/C/vinagre/scaling.page:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/C/vinagre/take-screenshot.page:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/C/vinagre/view-only.page:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/cs/vinagre/connect-file.page:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/cs/vinagre/connect-reverse.page:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/cs/vinagre/connect.page:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/cs/vinagre/figures/preferences-desktop-remote-desktop.png:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/cs/vinagre/figures/vinagre-connected-3-16.png:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/cs/vinagre/fullscreen.page:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/cs/vinagre/index.page:No 
such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/cs/vinagre/introduction.page:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/cs/vinagre/keyboard-shortcuts.page:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/cs/vinagre/legal.xml:No 
such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/cs/vinagre/scaling.page:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/cs/vinagre/take-screenshot.page:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/cs/vinagre/view-only.page:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/de/vinagre/connect-file.page:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/de/vinagre/connect-reverse.page:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/de/vinagre/connect.page:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/de/vinagre/figures/preferences-desktop-remote-desktop.png:No
 such file or directory
pkg-static: Unable to access file 
/usr/ports/net/vinagre/work/stage/usr/local/share/help/de/vinagre/figures/vinagre-connected-3-16.png:No
 such file or directory
pkg-static: Unable to access file 

Re: MESON_ARGS

[Walter Schwarzenfeld]

I did not manage to got MESON_ARGS to work (like CONFIGURE_ARGS as above).
___
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"

MESON_ARGS

[Walter Schwarzenfeld]

The only way to pass more than one argument from the Makefile to meson I 
got working is e.g:


CONFIGURE_ARGS= -Drpm=false
CONFIGURE_ARGS+=    -Dstemmer=false
CONFIGURE_ARGS+=    -Dintrospection=false

One arg in per row and in the order as in the meson_options.txt.

The "normal" way to break the line with a backslash does not work.

Is there another way (accept to patch meson_options.txt and meson.build)?

It is not very handy.

Can anyone tell me the right syntax?

___
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: graphics/evince

[The Doctor]

On Mon, Feb 19, 2018 at 06:50:39PM +0100, Kurt Jaeger wrote:
> Hi!
> 
> > I'm retesting right now. If all works out, I'll commit the patch.
> 
> Committed, thanks to all involved!
>

You are welcome.  I hope to find more.

> -- 
> p...@opsec.eu+49 171 3101372 2 years to 
> go !
> ___
> 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"

-- 
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 on Atheism
Not by age but by capacity is wisdom acquired.  -Titus Maccius Plautus
___
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: 6100 subdirectories in /usr/ports/devel!

[olli hauer]

On 2018-02-19 17:25, Dan Mahoney (Gushi) wrote:
> On Mon, 19 Feb 2018, blubee blubeeme wrote:

...

> 
> For those of us requiring a perl module on a bunch of machines, we don't have 
> a good mechanism (outside of ports/pkg/poudriere) to build those modules and 
> get them out.  One of the things pkgng lacks is the old ports "make pkg" 
> function -- in order to build an installable package, you pretty much must be 
> running poudriere.
> 


No, with pkgng you have several ways to create a package from a port.

On a system where the port is installed:

  $ mkdir -p $space/packages//All
  $ cd $space/packages
  $ pkg create -o $space/packages/All -x p5*
# optional if you want to distribute your packages create the pkg indexes
  $ pkg repo .

Now you have a repo with all your p5* packages, change "-x p5" to "-a" and you 
have a repo with all installed package, see man pkg-create(8)


If you want to create a package directly in the directory of the port

  $ mkdir -p $space/packages/All
  $ sysrc -f /etc/make.conf PACKAGES="$space/packages"
  $ cd $PORT
  $ make package

Now you have one package in $space/packages/All and one in $PORT/work/pkg
___
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: 6100 subdirectories in /usr/ports/devel!

[Kurt Jaeger]

Hi!

> On 02/19/2018 11:25 AM, Dan Mahoney (Gushi) wrote:
> > Several of the CPAN modules currently around today don't compile cleanly 
> > under FreeBSD, but nobody cares because they just use the package which 
> > has the additional patches.

> Do you have a list of those CPAN modules which don't compile cleanly on 
> FreeBSD?

Probably all p5-* ports with files/patch-* files -- that list can
easily be generated with a little script ?

> Speaking as a longtime CPAN contributor and as a recent FreeBSD ports 
> contributor, I'd like to see what can be done to maintain quality in 
> both archives.

That would be very helpful, indeed!

-- 
p...@opsec.eu+49 171 3101372 2 years to go !
___
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: graphics/evince

[Kurt Jaeger]

Hi!

> I'm retesting right now. If all works out, I'll commit the patch.

Committed, thanks to all involved!

-- 
p...@opsec.eu+49 171 3101372 2 years to go !
___
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: graphics/evince

[Kurt Jaeger]

Hi!

> > >> I just tried the patch to update evince-3.18.2_5 to evince-3.26.0 on
> > >> 12.0-CURRENT amd64 and it works for me.

> > > Works as in 'builds' or works as in 'runs' 8-} ?

> > Both, it builds, installs and runs fine, as far as I can say after
> > opening a few pdf files.

> Any chance for a commit?

I testbuild evince in poudriere, looks fine. I also testbuild
evince-lite, it failed with some pkg-plist inconsistencies.

I'm retesting right now. If all works out, I'll commit the patch.

-- 
p...@opsec.eu+49 171 3101372 2 years to go !
___
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: graphics/evince

[Greg Veldman]

On Sun, Feb 18, 2018 at 07:12:50PM +0100, Rainer Hurling wrote:
> Am 18.02.2018 um 19:02 schrieb Kurt Jaeger:
> > Hi!
> > 
> >>> Ah, there's a patch already at
> >>>
> >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221781
> >>>
> >>> Can you test if it works for you ?
> > 
> >> I just tried the patch to update evince-3.18.2_5 to evince-3.26.0 on
> >> 12.0-CURRENT amd64 and it works for me.
> > 
> > Works as in 'builds' or works as in 'runs' 8-} ?
> > 
> 
> Both, it builds, installs and runs fine, as far as I can say after
> opening a few pdf files.

I can confirm that the referenced patch also works for me on
an up-to-date 11.1-RELEASE amd64 system.  It builds cleanly and
works as expected.  Tested for both evince and evince-lite.

I'll second the request to get this committed.

Thanks.

-- 
Greg Veldman
g...@gregv.net
___
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: pkg check --recompute and apache24 deleted files

[Rafal Lukawiecki]

For what it may be worth, I have submitted a bug report about this unexpected 
behaviour of pkg check --recompute. See 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226048 
 

Rafal

___
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: 6100 subdirectories in /usr/ports/devel!

[James E Keenan]

On 02/19/2018 11:25 AM, Dan Mahoney (Gushi) wrote:


Several of the CPAN modules currently around today don't compile cleanly 
under FreeBSD, but nobody cares because they just use the package which 
has the additional patches.




Do you have a list of those CPAN modules which don't compile cleanly on 
FreeBSD?


Have bug tickets been open for those problems?

Speaking as a longtime CPAN contributor and as a recent FreeBSD ports 
contributor, I'd like to see what can be done to maintain quality in 
both archives.


Thank you very much.
Jim Keenan

___
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: 6100 subdirectories in /usr/ports/devel!

[Dan Mahoney (Gushi)]

On Mon, 19 Feb 2018, blubee blubeeme wrote:


I agree with this as well, why maintain these ports when they're being
maintained upstream. Plus, if we do need patches, they can be applied
during the build step.



maybe with the ability to add some patches on the way through.. There is
just too much going on there for us to follow properly.



I double this thought! This is what I'm goinf to head to with Haskell ports
one time.

There is a hitch, though. Hackage, the haskell package database, is a dump.
You easily can get a version clash between to packages. No one curates
them. So, while there was only Hackage maintaining hs- ports made sense -
we've been cheking all the packages we have to compile/work together. But
now Stackage emerged, which is a curated package DB, so our ports is a
duplicated work now. The port is only needed if it is not present on
Stackage or if it require FreeBSD specific patches that haven't been
upstreamed yet.

If PyPi and CPAN has the same notion of curated package set, we should not
duplicate this effort and remove much of our py- and p5- ports.


I'm going to speak only about perl here, but there's no reason that this 
advice couldn't apply to other languages.  I have some history, and some 
suggestions.


History:

CPAN distributes source, not binaries.  Ports delivers an instruction set 
to build binaries.  Some of the CPAN packages are written in C (for 
securtiy, speed, or linkability against other C/System libraries) and 
require compilation.


For those of us requiring a perl module on a bunch of machines, we don't 
have a good mechanism (outside of ports/pkg/poudriere) to build those 
modules and get them out.  One of the things pkgng lacks is the old ports 
"make pkg" function -- in order to build an installable package, you 
pretty much must be running poudriere.


Several of the CPAN modules currently around today don't compile cleanly 
under FreeBSD, but nobody cares because they just use the package which 
has the additional patches.


A few years ago, under pkg-classic, we had this thing called BSDPAN, which 
meant that if you installed a perl module using perl -MCPAN -e 'install 
Bundle::CPAN' those installations would get added in a pseudo-fashion to 
the pkg database.  This doesn't exist anymore.


I use pkg because I don't want to build perl, python, and libx11 from 
scratch so I can run a webserver.  On the same note, I use FreeBSD perl 
packages because I don't feel like chasing the endless CPAN dependency 
chain, which may or may not fail eight levels deep and stopping my build.


I'd love to know how you propose to solve the above before deciding that 
all the people who use Perl and Python ports consider the (mostly working) 
ports to be "someone else's problem".


Suggestions:

What I might suggest is that we split off the ports tree such that you can 
optionally not fetch portions of it -- for example, throwing a warning 
that you need the perl modules if trying to build a port with uses_perl5. 
Right now, that's not how the ports are arranged -- as an example, right 
now p5-Net-SSLEAY is under ports/security, not ports/perl5/security.


From there, you might maintain a whitelist of perl ports which build 
exactly with only a standard set of arguments (i.e. setting Prefix, etc), 
so that you can, in needing perl ports, just *use* the standard perl build 
tools, instead of a skeleton port for each.


You might still need to have perl ports that require more "surgery" to 
work right, or CPAN modules for which the maintainer has gone away or 
retired (it's perl, after all), but it's a reduced subset which would be 
easlier to maintain/fetch/update.


You might bring back BSDPAN in some form or another -- how exactly it 
would work depends on what happens with this in the future, so that perl 
things installed from pkg, and those built from CPAN don't conflict.


We could make it so the build system knows how to fetch on demand the 
"extra" trees it requires.


We could also go through the ports tree and see which perl modules are 
solely leaf nodes, and not required (optionally or directly) by any other 
ports, and move those to a different list or subtree -- in those cases, 
the only stakeholder is someone writing code that directly requires that 
module -- you won't cause a cascading build breakage if that port vanishes 
or fails.


A lot of this feels like it wants to wait for the pkg system to support 
"flavors" so we can turn off the language specific options.


-Dan

--

Dan Mahoney
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
FB:  fb.com/DanielMahoneyIV
LI:   linkedin.com/in/gushi
Site:  http://www.gushi.org
---


___
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: 6100 subdirectories in /usr/ports/devel!

[blubee blubeeme]

On Mon, Feb 19, 2018 at 7:56 PM, Gleb Popov <6year...@gmail.com> wrote:

> On Mon, Feb 19, 2018 at 9:45 AM, Julian Elischer 
> wrote:
>
> > On 29/12/17 5:16 am, Bob Willcox wrote:
> >
> >> On Fri, Dec 29, 2017 at 03:54:28AM +0700, Eugene Grosbein wrote:
> >>
> >>> 29.12.2017 3:36, Bob Willcox wrote:
> >>>
> >>> Does anyone else feel that having 6100 subdirectories (939 are for py-*
> > stuff)
> > is a bit excessive?
> >
>  It is. But py-* stuff has second place only:
> 
>  $ ls /usr/ports/devel | sed 's/-.*//' | sort | uniq -c | sort -rn |
> head
>  1908 p5
>    964 py
>    600 rubygem
>    280 hs
>    176 pear
> 57 R
> 56 pecl
> 48 elixir
> 47 geany
> 43 erlang
> 
> >>> In fact, ports/devel is first but not only category having similar
> >>> problem with p5-* stuff:
> >>>
> >>> $ cd /usr/ports
> >>> $ find . -type d -mindepth 1 -maxdepth 1 | while read category; do
> >>> printf "%15s " ${category#./}; ls $category | sed 's/-.*//' | sort |
> uniq
> >>> -c | sort -rn | head -1; done | sort -k 2,2 -rn | head -15
> >>>devel 1908 p5
> >>>  www  807 p5
> >>> textproc  617 p5
> >>>  net  327 p5
> >>>databases  259 p5
> >>> security  258 p5
> >>> math  146 p5
> >>> mail  145 p5
> >>> graphics  100 p5
> >>>  editors   98 libreoffice
> >>> sysutils   75 rubygem
> >>>   converters   72 p5
> >>> misc   63 p5
> >>> net-mgmt   56 p5
> >>> x11-toolkits   49 p5
> >>>
> >>> Yeah, I happened to notice the py-* stuff due to some problems I have
> >> been
> >> having with synth. I did notice the large number of p5-* subdirs but
> >> didn't
> >> count them.  :)
> >>
> >> Certainly seems to be out of control...
> >>
> >> the py and p5 stuff is a symptom of another problem, which is that we
> are
> > only second level for those files...
> >
> > the correct behaviour in my point of view is for our packages/ports
> system
> > to delegate to pypi or similar for python and to CPAN for perl.
>
I agree with this as well, why maintain these ports when they're being
maintained upstream. Plus, if we do need patches, they can be applied
during the build step.

> >
> > maybe with the ability to add some patches on the way through.. There is
> > just too much going on there for us to follow properly.
>
>
> I double this thought! This is what I'm goinf to head to with Haskell ports
> one time.
>
> There is a hitch, though. Hackage, the haskell package database, is a dump.
> You easily can get a version clash between to packages. No one curates
> them. So, while there was only Hackage maintaining hs- ports made sense -
> we've been cheking all the packages we have to compile/work together. But
> now Stackage emerged, which is a curated package DB, so our ports is a
> duplicated work now. The port is only needed if it is not present on
> Stackage or if it require FreeBSD specific patches that haven't been
> upstreamed yet.
>
> If PyPi and CPAN has the same notion of curated package set, we should not
> duplicate this effort and remove much of our py- and p5- ports.
>
>
> >
> >
> > ___
> > 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@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@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Cannot require library for passenger in ruby

[Karli Sjöberg via freebsd-ports]

On Mon, 2018-02-19 at 07:50 +, Marcin Cieslak wrote:
> On Mon, 19 Feb 2018, Karli Sjöberg wrote:
> 
> > 
> > 
> > Den 18 feb. 2018 23:49 skrev Marcin Cieslak :
> >   On Sat, 17 Feb 2018, Karli Sjöberg via freebsd-ports wrote:
> >   CONFIG
> >   > /usr/local/lib/ruby/gems/2.4/gems/foreman_maintain-
> > 0.1.3/bin/passenger-recycler:8: warning: previous definition of
> > CONFIG
> >was here
> >   >
> > /usr/local/lib/ruby/site_ruby/2.4/rubygems/core_ext/kernel_require.
> > rb:135:in `require': cannot load such file --
> >   /phusion_passenger/utils/tmpio (LoadError)
> >   > from
> > /usr/local/lib/ruby/site_ruby/2.4/rubygems/core_ext/kernel_require.
> > rb:135:in `rescue in require'
> >   > from
> > /usr/local/lib/ruby/site_ruby/2.4/rubygems/core_ext/kernel_require.
> > rb:39:in `require'
> >   > from /usr/local/lib/ruby/gems/2.4/gems/passenger-
> > 5.2.0/src/ruby_supportlib/phusion_passenger.rb:240:in
> >   `require_passenger_lib'
> >   > from /usr/local/lib/ruby/gems/2.4/gems/passenger-
> > 5.2.0/src/ruby_supportlib/phusion_passenger/platform_info.rb:26:in
> >   `'
> > 
> >   Where did you get passenger 5.2.0?
> > 
> >   Can you try to install passenger 5.1.12 from ports and see if
> > it works better?
> > 
> > 
> > Right, yeah, no, I started with 5.1.12 from ports and when it
> > didn't work, I installed a newer version with 'gem'. I can
> > deinstall it
> > again if you want to see the backtrace?
> 
> Would be good, please. 

irb(main):001:0> require 'phusion_passenger'
=> true
irb(main):002:0> PhusionPassenger.require_passenger_lib 'utils/tmpio'
LoadError: cannot load such file -- /phusion_passenger/utils/tmpio
from 
/usr/local/lib/ruby/site_ruby/2.4/rubygems/core_ext/kernel_require.rb:135:in 
`require'
from 
/usr/local/lib/ruby/site_ruby/2.4/rubygems/core_ext/kernel_require.rb:135:in 
`rescue in require'
from 
/usr/local/lib/ruby/site_ruby/2.4/rubygems/core_ext/kernel_require.rb:39:in 
`require'
from 
/usr/local/lib/ruby/gems/2.4/gems/passenger-5.1.12/src/ruby_supportlib/phusion_passenger.rb:240:in
 `require_passenger_lib'
from (irb):2
from /usr/local/bin/irb:11:in `'
irb(main):003:0> require 'phusion_passenger/utils/tmpio'
=> true

> I wonder how many passenger dependencies got installed via rubygems -
> would be good to
> have them restored, too. 

None, that I could see.

> What is the tool you are trying to deploy? foreman_maintain?

Exactly!

/K

> 
> Marcin

signature.asc
Description: This is a digitally signed message part

Re: 6100 subdirectories in /usr/ports/devel!

[Gleb Popov]

On Mon, Feb 19, 2018 at 9:45 AM, Julian Elischer  wrote:

> On 29/12/17 5:16 am, Bob Willcox wrote:
>
>> On Fri, Dec 29, 2017 at 03:54:28AM +0700, Eugene Grosbein wrote:
>>
>>> 29.12.2017 3:36, Bob Willcox wrote:
>>>
>>> Does anyone else feel that having 6100 subdirectories (939 are for py-*
> stuff)
> is a bit excessive?
>
 It is. But py-* stuff has second place only:

 $ ls /usr/ports/devel | sed 's/-.*//' | sort | uniq -c | sort -rn | head
 1908 p5
   964 py
   600 rubygem
   280 hs
   176 pear
57 R
56 pecl
48 elixir
47 geany
43 erlang

>>> In fact, ports/devel is first but not only category having similar
>>> problem with p5-* stuff:
>>>
>>> $ cd /usr/ports
>>> $ find . -type d -mindepth 1 -maxdepth 1 | while read category; do
>>> printf "%15s " ${category#./}; ls $category | sed 's/-.*//' | sort | uniq
>>> -c | sort -rn | head -1; done | sort -k 2,2 -rn | head -15
>>>devel 1908 p5
>>>  www  807 p5
>>> textproc  617 p5
>>>  net  327 p5
>>>databases  259 p5
>>> security  258 p5
>>> math  146 p5
>>> mail  145 p5
>>> graphics  100 p5
>>>  editors   98 libreoffice
>>> sysutils   75 rubygem
>>>   converters   72 p5
>>> misc   63 p5
>>> net-mgmt   56 p5
>>> x11-toolkits   49 p5
>>>
>>> Yeah, I happened to notice the py-* stuff due to some problems I have
>> been
>> having with synth. I did notice the large number of p5-* subdirs but
>> didn't
>> count them.  :)
>>
>> Certainly seems to be out of control...
>>
>> the py and p5 stuff is a symptom of another problem, which is that we are
> only second level for those files...
>
> the correct behaviour in my point of view is for our packages/ports system
> to delegate to pypi or similar for python and to CPAN for perl.
>
> maybe with the ability to add some patches on the way through.. There is
> just too much going on there for us to follow properly.


I double this thought! This is what I'm goinf to head to with Haskell ports
one time.

There is a hitch, though. Hackage, the haskell package database, is a dump.
You easily can get a version clash between to packages. No one curates
them. So, while there was only Hackage maintaining hs- ports made sense -
we've been cheking all the packages we have to compile/work together. But
now Stackage emerged, which is a curated package DB, so our ports is a
duplicated work now. The port is only needed if it is not present on
Stackage or if it require FreeBSD specific patches that haven't been
upstreamed yet.

If PyPi and CPAN has the same notion of curated package set, we should not
duplicate this effort and remove much of our py- and p5- ports.


>
>
> ___
> 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@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

[portscout]

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
+-+
devel/lua-posix | 34.0.1  | v34.0.2
+-+


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: Why no `operator delete(void*, unsigned int)' on 10 i386?

[Yuri]

On 02/18/18 22:46, Fernando Apesteguía wrote:

Those are sized operators from c++14. Have you tried to compile with:
-std=gnu++11?



Thank you, but it didn't help in my case.


Yuri

___
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"