Re: harder and harder to avoid pkg

2016-10-14 Thread David Demelier
2016-10-14 8:14 GMT+02:00 Loïc BLOT : > FreeBSD ports are complicated ? > Does someone of you tryed to do a Debian package, it's even more > complicated as you should modify many path, split package in multiple > packages, do the service engineering with systemV or systemD, etc ? It's not writing

Re: harder and harder to avoid pkg

2016-10-14 Thread Julian Elischer
On 13/10/2016 5:42 AM, David Demelier wrote: 2016-10-12 10:04 GMT+02:00 Andrea Venturoli : On 10/12/16 09:24, Matthieu Volat wrote: And GNU/Linuxes can be a PITA when you have to track -dev(el) packages (which sometimes really requires -bin, -app or whatever), or worst, describe to people how

Re: harder and harder to avoid pkg

2016-10-14 Thread Julian Elischer
On 13/10/2016 10:33 AM, RW via freebsd-ports wrote: On Tue, 11 Oct 2016 11:59:47 -0700 Julian Elischer wrote: As the number of dependencies between packages get ever higher, it becomes more and more difficult to compile packages and the dependence on binary precompiled packages is increased. Ho

gcc5 dependency challenges

2016-10-14 Thread Dewayne Geraghty
After some rudimentary performance testing I note that we get up around 3% improvement in application performance when we use gcc5 for our package builds. However building ports with gcc results in gcc5 being a dependency. Examining ldd, we find that rarely does anything require gcc5's shared libs

Re: harder and harder to avoid pkg

2016-10-14 Thread Mathieu Arnold
Le 14/10/2016 à 09:34, Julian Elischer a écrit : > On 13/10/2016 5:42 AM, David Demelier wrote: >> 2016-10-12 10:04 GMT+02:00 Andrea Venturoli : >>> On 10/12/16 09:24, Matthieu Volat wrote: >>> And GNU/Linuxes can be a PITA when you have to track -dev(el) packages (which sometimes really

Re: gcc5 dependency challenges

2016-10-14 Thread Julian Elischer
On 14/10/2016 12:48 AM, Dewayne Geraghty wrote: After some rudimentary performance testing I note that we get up around 3% improvement in application performance when we use gcc5 for our package builds. However building ports with gcc results in gcc5 being a dependency. Examining ldd, we find th

www/magento port outdated

2016-10-14 Thread Alexander Liebau
hello, i would like to ask if it is possible to update the port www/magento to its current version. it is currently on version 1.8.1 which is more than 2 years old. the most recent version would be 2.1.2 or 2.0.10 according to https://www.magentocommerce.com/download kind regards, Alexander

Re: harder and harder to avoid pkg

2016-10-14 Thread Baptiste Daroussin
On Fri, Oct 14, 2016 at 09:54:07AM +0200, Mathieu Arnold wrote: > Le 14/10/2016 à 09:34, Julian Elischer a écrit : > > On 13/10/2016 5:42 AM, David Demelier wrote: > >> 2016-10-12 10:04 GMT+02:00 Andrea Venturoli : > >>> On 10/12/16 09:24, Matthieu Volat wrote: > >>> > And GNU/Linuxes can be a

Re: www/magento port outdated

2016-10-14 Thread Kurt Jaeger
Hi! > i would like to ask if it is possible to update the port www/magento to > its current version. > it is currently on version 1.8.1 which is more than 2 years old. > the most recent version would be 2.1.2 or 2.0.10 according to > https://www.magentocommerce.com/download Can you provide a pa

Re: www/magento port outdated

2016-10-14 Thread Torsten Zuehlsdorff
On 14.10.2016 11:13, Alexander Liebau wrote: hello, i would like to ask if it is possible to update the port www/magento to its current version. it is currently on version 1.8.1 which is more than 2 years old. the most recent version would be 2.1.2 or 2.0.10 according to https://www.magentocom

Re: gcc5 dependency challenges

2016-10-14 Thread Kubilay Kocak
On 14/10/2016 6:48 PM, Dewayne Geraghty wrote: > After some rudimentary performance testing I note that we get up > around 3% improvement in application performance when we use gcc5 for > our package builds. > > However building ports with gcc results in gcc5 being a dependency. > Examining ldd,

Re: harder and harder to avoid pkg

2016-10-14 Thread Matthew Seaman
On 10/14/16 10:22, Baptiste Daroussin wrote: > We could imagine tagging the plist/manifest so pkg can allow a user to install > only the things tagged as runtime for exemple which would do the job. for what > Julian is asking for beside adding lots of complexity pkg(8) and adding a > nightmare in t

Re: www/magento port outdated

2016-10-14 Thread Torsten Zuehlsdorff
On 14.10.2016 12:15, Torsten Zuehlsdorff wrote: On 14.10.2016 11:13, Alexander Liebau wrote: hello, i would like to ask if it is possible to update the port www/magento to its current version. it is currently on version 1.8.1 which is more than 2 years old. the most recent version would be

Re: harder and harder to avoid pkg

2016-10-14 Thread David Demelier
2016-10-14 11:22 GMT+02:00 Baptiste Daroussin : > It is imho doable in both sides. > > We could imagine tagging the plist/manifest so pkg can allow a user to install > only the things tagged as runtime for exemple which would do the job. for what > Julian is asking for beside adding lots of complex

Re: harder and harder to avoid pkg

2016-10-14 Thread Jan Bramkamp
On 14/10/2016 09:39, Julian Elischer wrote: On 13/10/2016 10:33 AM, RW via freebsd-ports wrote: On Tue, 11 Oct 2016 11:59:47 -0700 Julian Elischer wrote: As the number of dependencies between packages get ever higher, it becomes more and more difficult to compile packages and the dependence on

Re: harder and harder to avoid pkg

2016-10-14 Thread Kurt Jaeger
Hi! > > This is an appliance class machine. It has 2G of storage and that has > > to include 2 copies for the OS so we can ping-pong for upgrades. > > I can get > 2GB CPU cache per system (spread over 8+ sockets) these > days. Is it really reasonable to expect port maintainers to take up the >

Re: harder and harder to avoid pkg

2016-10-14 Thread Matthieu Volat
On Fri, 14 Oct 2016 13:05:35 +0200 David Demelier wrote: > 2016-10-14 11:22 GMT+02:00 Baptiste Daroussin : > > It is imho doable in both sides. > > > > We could imagine tagging the plist/manifest so pkg can allow a user to > > install > > only the things tagged as runtime for exemple which would

Re[2]: www/magento port outdated

2016-10-14 Thread Alexander Liebau
a new port would be quite nice. i am pretty clueless about creating or maintaining one though :( regards, alex -- Originalnachricht -- Von: "Torsten Zuehlsdorff" An: "Alexander Liebau" ; po...@freebsd.org Gesendet: 14.10.2016 12:49:12 Betreff: Re: www/magento port outdated On 14.10

Re: harder and harder to avoid pkg

2016-10-14 Thread Julian Elischer
On 14/10/2016 4:27 AM, Matthieu Volat wrote: On Fri, 14 Oct 2016 13:05:35 +0200 David Demelier wrote: 2016-10-14 11:22 GMT+02:00 Baptiste Daroussin : It is imho doable in both sides. We could imagine tagging the plist/manifest so pkg can allow a user to install only the things tagged as runt

The Unique iMarketing Center app to send bulk SMS and email

2016-10-14 Thread iMarketing Center
___ 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: harder and harder to avoid pkg

2016-10-14 Thread Dave Horsfall
On Fri, 14 Oct 2016, David Demelier wrote: > It's not writing a port that is complicated, it's the whole > infrastructure. You should see the Macports infrastructure... Fairly easy for the end user, but those developers sweat blood to make it so. -- Dave Horsfall DTM (VK2KFU) "Those who don

Looking for a committer net-mgmt/prometheus

2016-10-14 Thread Jev Björsell
Hi All, I just updated https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212468 patch attachment to build the latest release of prometheus. It's now 1.2.1 Can I get a committer to review, and possibly commit? This new port request and my other one (node_exporter: https://bugs.freebsd.org/bugzilla

Re: Looking for a committer net-mgmt/prometheus

2016-10-14 Thread Kurt Jaeger
Hi! > I just updated https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212468 patch > attachment to build the latest release of prometheus. It's now 1.2.1 Well, the version number in the patch was 1.1.3, but changing that to 1.2.1 was easy, test-building was OK, so: done. > Can I get a committer