Re: Creating port from pre-built package

On 11/02/2021 16:26, Shawn Webb wrote: Being a ports newb, I'm not sure how to properly create a port from a pre-built package. Does anyone have any non-xkcd pointers[1]? A port is simply a set of instructions to build a pkg. So you're looking for a set of instructions to build a pkg from a

Re: FreeBSD Port: pgbarman-2.11

On 06/11/2020 20:17, Ryan Quinn wrote: > Hi Matthew! > > Would it be possible to get barman to support multiple versions of postgres? > > Here’s the background. > > I’m testing barman as a backup solution, and I upgraded barman to version > 2.11 on my test system. I wasn’t paying attention, so

Re: [HEADS UP] Planned deprecation of portsnap

On 09/08/2020 07:03, Stefan Ehmann wrote: > I usually run `pkg version` to see what packages have changed. > > Previously, that was a more or less instant operation, now it takes over 100 > seconds. The problem is that /usr/ports/INDEX-12 is missing. Yes. For historical reason, the order of

Re: Lsof port can't build (again)

On 17/06/2020 04:23, @lbutlr wrote: > Thank you, cleared /usr/src and running the svn checkout with that > URL now. It's still well over a gig so it will be a few minutes > before trying to build lsof again. Alas, it is a bit late now, but next time you need to switch branches like this, use `svn

Re: Ports from github

On 25/05/2020 03:55, Adam Weinberger wrote: > Thank you, Matthew! This is such gold. Could you maybe dump that into > a page on the FreeBSD wiki? It'd be nice to have in the PHB but wiki > would be a great start. Clear explanations like this are precisely > what users need, and we need to start

Re: Ports from github

On 24/05/2020 03:39, Montgomery-Smith, Stephen wrote: > Is there a "howto" that explains how to build a port from a project that > is on github? The FreeBSD porters handbook seems to assume a lot of > knowledge is already understood. Well, the only thing "different" about porting something from

Re: python 2.7 marked as deprecated and EOL while 2.7.18 RC is available

On 18/04/2020 03:19, Robert Huff wrote: > a) according to the Makefile, is it possible to build this with > python-37? (Or even -36?) If the Makefile for the port says: USES= python:27 then the port is for python-2.7.x only. All other python ports will support python-3.x

Re: Notifying maintainers when their port is labeled BROKEN would make a difference

On 18/02/2020 17:20, Yuri wrote: > Currently maintainers aren't notified when their ports are labeled broken. > > Adding broken ports to "Issues that need your attention" e-mails would > make a difference. > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243271 > > Who can make this

Re: Portmaster failing

On 01/01/2020 22:03, George Mitchell wrote: > Assuming you can get poudriere to work. Even by today's standards, > a low-cost PC is not going to have the juice to support it. And to > reiterate, the ports framework itself MUST work standalone. Rubbish. I maintain my own poudriere repo on a

Re: python distutils without setup.py?

On 08/12/2019 18:16, Po-Chuan Hsieh wrote: > For now, you could try using the patched setup.py from current version [1]: > > import setuptools > if __name__ == "__main__": > setuptools.setup(use_scm_version=True) > > At least it works for me for sysutils/py-ansible-lint 4.2.0. Good idea.

Re: python distutils without setup.py?

On 05/12/2019 07:36, Matthew Seaman wrote: > There's a comment in the ChangeLog: > >* Fully depend on Pip having PEP 517 implementation #607 > > and the associated merge: > >https://github.com/ansible/ansible-lint/pull/607/files > > has the removal of

python distutils without setup.py?

I'm looking at updating sysutils/py-ansible-lint (https://github.com/ansible/ansible-lint) and it's got me scratching my head. Seems there's now no setup.py included in the source code, and that makes the ports sad: ``` lucid-nonsense:~...ports/sysutils/py-ansible-lint:% make ===> License MIT

Re: Many ports recently marked BROKEN/unfetchable that aren't broken?

On 15/11/2019 15:25, Nick Rogers wrote: For me the affected ports were sysutils/pftop, sysutils/zfs-stats, and sysutils/stress, which worked just fine before this commit. Apologies if I am missing something, but it seems like they are not actually broken? If you were building these ports

Re: "poudriere testport" to download binary depends

On 21/10/2019 14:59, John Kennedy wrote: On Mon, Oct 21, 2019 at 01:59:17PM +0100, Matthew Seaman wrote: On 21/10/2019 13:31, Sergei Vyshenski wrote: Is it possible to instruct "poudriere testport" such that it downloads depends (in a form of binary packages) from the central

Re: "poudriere testport" to download binary depends

On 21/10/2019 13:31, Sergei Vyshenski wrote: Is it possible to instruct "poudriere testport" such that it downloads depends (in a form of binary packages) from the central repository, and actually tests only the port in question? Currently, no this is not available. Using another repo to

Re: Ansible playbooks for building a poudriere test system

On 23/09/2019 14:27, Bernhard Fröhlich wrote: > On Mon, Sep 23, 2019 at 10:27 AM Matthew Seaman wrote: >> >> Hi, >> >> I put this together as the basis of the class I gave at EuroBSDCon a few >> days ago, and I thought I'd share it as it might prove us

Ansible playbooks for building a poudriere test system

Hi, I put this together as the basis of the class I gave at EuroBSDCon a few days ago, and I thought I'd share it as it might prove useful: https://github.com/infracaninophile/p4pm This should be able to take an 'as installed' FreeBSD machine with just a local user account added, or the

Re: make index produces 0 byte INDEX-11

On 25/07/2019 10:42, Andy Farkas wrote: make_index: /usr/ports/archivers/atool: no entry for /usr/ports/:lang/perl5.26  Done. 1533.047u 907.912s 8:12.79 495.3%    23786+867k 500780+163017io 13720pf+0w root:/usr/ports # ls -l INDEX-11 -rw-r--r--  1 root  wheel  0 Jul 25 19:07 INDEX-11

Anyone want to take over these ports?

Dear all, I should have done this years ago, but I am an extremely skilled prevaricator and it seems that only now is finally the time... MySQL is no-longer part of my life, so I'd like to off-load some MySQL related ports: databases/mysql-connector-java databases/mysql-connector-java51

Re: How to best check a configuration of another port/package?

On 13/06/2019 17:00, Steve Wills wrote: Hmm, flavors have to be something that can be installed in parallel, right? How does that impact binutils? They don't /have/ to be something that can be installed in parallel. Different flavours of the same package can conflict with each other. Look at

Re: Cleaning up pkg-message

On 08/06/2019 19:29, Bob Eager wrote: > The committer folded the README file into pkg-message, and I disagree > with this: > 2) It meant that an end user (without access to the ports tree) didn't > have an immediate way to see the README contents. That's not actually correct. ``` % pkg info -D

Re: GSoC: Separation of Ports Build Process from Local Installation

On 29/05/2019 10:56, Peter Pentchev wrote: Hmm, I could be wrong, but isn't ${LOCALBASE} supposed to be where ports find stuff*during the build*, and ${PREFIX} where they install the built files? Of course, I haven't actually touched a FreeBSD ports build in years, so I might very likely be

Re: How to use @preexec to test for installed packages

On 06/04/2019 14:58, Matthias Fechner wrote: > as pkg cannot handle CONFLICTS_INSTALL I tried now to implement this as > a preinstall command using @preexec in pkg-plist. > > The command should check if a package is installed and stop the > installation or continue if the package is not

Re: Fwd: FreeBSD ports you maintain which are out of date

On 16/03/2019 21:08, Alfred Perlstein wrote: > How do I stop these emails? > > I just retired my commit bit and stopped committing to ports after some > folks yelled at me for committing to ports without signoff even though I > was doing ports before the src/ports split. > > thanks, > > -Alfred

Re: Django versions

On 07/03/2019 07:22, Antoine Brodin wrote: > Please don't use the django metaport, this port should be removed and > people should stop using hacks. > Someone needs to integrate a USE_PYTHON=django in python.mk Let me look at that. I never did like leaving D12592 so unresolved. Although it

Re: Deregister a port?

On 04/02/2019 14:22, Luciano Mannucci wrote: > On Mon, 4 Feb 2019 13:38:56 + > Matthew Seaman wrote: > >> Tell us the details and we may be able to help. > Well, I'm migrating some web servers from very old linux to freebsd. > I need several versions of php

Re: Deregister a port?

On 04/02/2019 12:14, Luciano Mannucci wrote: > Is there a way to deregister a port without touching port's files? Only by futzing with the package database directly, which is not recommended. Why would you want to do this anyway? Misleading the pkg database as to what is actually installed on

Re: py27 ./. py3 version of ports

On 10/01/2019 11:58, Matthias Apitz wrote: El día jueves, enero 10, 2019 a las 11:14:19a. m. +, Matthew Seaman escribió: On 10/01/2019 10:04, Matthias Apitz wrote: I've compiled on CURRENT the ports of December 23 from SVN with my poudriere oven. ANd I have nothing set about FLAVOR

Re: py27 ./. py3 version of ports

On 10/01/2019 10:04, Matthias Apitz wrote: I've compiled on CURRENT the ports of December 23 from SVN with my poudriere oven. ANd I have nothing set about FLAVOR in make.conf for python. Why d I habe now some 157 py27 ports and only 4 py3: $ ls -l /usr/PKGDIR.20181223/py27* | wc -l 157 $

Re: Updating perl

On 14/12/2018 10:44, Carmel NY wrote: > Using poudriere, I attempted to update my system to the new "perl 5.28". I > made the necessary changes in the "make.conf" files and then attempted to run > poudriere. At the very beginning of the run, poudriere issued a warning that > "security/py-certbot |

Re: A potential new porter seeking some clarifications

On 13/12/2018 14:41, Arthur Pirika wrote: 1. If I understand correctly, the version of the ports tree as fetched by portsnap isn’t the best for working on the tree. I should instead make another copy of the tree as an svn checkout? Distfiles, however, still go to /usr/ports/distfiles If

Re: certbot lost certificates , and registration data

On 10/12/2018 14:54, Kubilay Kocak wrote: On 11/12/2018 1:43 am, Matthew Seaman wrote: On 10/12/2018 14:10, Paul Macdonald via freebsd-ports wrote: On 10/12/2018 13:15, Paul Macdonald via freebsd-questions wrote: Is anyone else seeing py-certbot having lost all installed certs

Re: certbot lost certificates , and registration data

On 10/12/2018 14:10, Paul Macdonald via freebsd-ports wrote: On 10/12/2018 13:15, Paul Macdonald via freebsd-questions wrote: Is anyone else seeing py-certbot having lost all installed certs, and the initial registation data? There was an update on the 7th Upgrade of

Re: pkg falls behind port version - how do ports become pkg's?

On 12/11/2018 14:58, Karl Pielorz wrote: How long does it usually take for an updated port (e.g. mysql56-server which in ports is at 5.6.42) to be available as a pkg? (pkg under FBSD 11.2 is currently 5.6.41). Which branch are you trcking in your pkg(8) config? If it's 'latest', then you'll

Re: Few how-it-works questions

On 11/11/2018 12:34, Grzegorz Junka wrote: > Hi All, > > I would like to understand a bit better how the ports infrastructure works. > > 1. Recommended way of upgrading ports is "poudriere ports -p local -u", > right? But this always gets me the latest version, in which some ports > may not

Re: orphaned: www/suphp

On 20/10/2018 16:28, Lorenzo Salvadore via freebsd-ports wrote: >> I just updated my ports tree and then proceeded to run: "pkg version -vL=" >> which produced this: >> >> suphp-0.7.2_2 ? orphaned: www/suphp >> >> There is nothing about this in either the UPDATING or MOVED files. Has this >> port

Re: python ports -- setuptools requiring the pbr module and failing on denied network access?

On 22/09/2018 19:13, Ruslan Makhmatkhanov wrote: > As for your question: > pbr is set in molecule's setup.py as setup_depends, so it should go to > BUILD_DEPENDS in Makefile. Also make sure that you list all the > dependencies from the molecule's requirements.txt as RUN_DEPENDS. That's fixed it,

python ports -- setuptools requiring the pbr module and failing on denied network access?

So, I've been working on porting molecule (https://pypi.org/project/molecule/), and I have a port that /almost/ works. I can compile and run molecule from my shell prompt using the port. Everything seems fine. Except when I try and build the port inside poudriere. It seems that python

Re: poudriere, FLAVOR and rebuilding for python3.6

On 09/09/2018 19:34, Bjarne wrote: > > I have been using python 2.7 so far for all ports, which means all > python packages  are built as py27-something. These python packages are > all automaticcaly build as dependencies from other packages, for example > like py27-dnspython which is a

Re: getting PKGNAME from CONFLICTS

On 15/08/2018 00:35, Dan Langille wrote: >> On Aug 14, 2018, at 2:55 PM, Mark Millard via freebsd-ports >> wrote: >> >> >> Dan Langille dan at langille.org wrote on >> Tue Aug 14 17:54:01 UTC 2018 : >> >>> . . . >>> At https://dev.freshports.org/www/p5-CGI/ you can see: >>> >>> CONFLICTS:

Re: how to make ports not install xorg or dependencies

On 31/07/2018 11:41, tech-lists wrote: Hello, context: freebsd-12 r336215 arm64 I don't want xorg or X11 or any of its components installed on this system. I install ports in the traditional way, in other words cd port && make config && make install. Any ports that in a generic config want

Re: make[1]: cannot open Makefile for new custom port

On 23/06/2018 19:36, Joseph Ward wrote: > I'm attempting to use make makeplist to create the initial pkg-plist as > there are a lot of files present, and I'm getting the following error: > > # make makeplist > ===>  License BSD4CLAUSE accepted by the user > ===>   nebula-db-0.1 depends on file:

Re: Removing git dependencies on perl5 and python27

On 17/06/2018 10:42, Yasuhiro KIMURA wrote: > I'm not sure if P4 option should be enabled by default. But I think it > is incosistent that default valued of P4 options is on while that of > SVN options is off. Given Perforce no longer supports FreeBSD as a server platform and the FreeBSD

Re: make package "*** Error code 1"

On 07/06/2018 21:17, Eugene Grosbein wrote: > 08.06.2018 8:12, duckmanjbr wrote: > >> do-install: >> ${MKDIR} ${STAGEDIR}${PREFIX}/pkg >> ${MKDIR} ${STAGEDIR}${PREFIX}/bin/localrepo >> ${MKDIR} ${STAGEDIR}/etc/inc/priv >> ${MKDIR} ${STAGEDIR}${DATADIR} >> ${INSTALL_DATA}

Re: How to debug this...

On 27/05/2018 08:58, Tobias Kortkamp wrote: > Check permissions on sysutils/rsyslog8/*. The PORTBUILD_USER > (probably 'nobody') needs to be able to read them. Yup. That was it. I just knew it was something stupidly obvious in retrospect. Thanks, and thanks to antoine for the same advice on

Re: How to debug this...

On 26/05/2018 23:08, Matthew Seaman wrote: > Given what you say, I'm pretty sure this is something peculiar to my > system, but I can't see what's causing the effect I'm seeing. > Hmmm I'm getting the same result on a new poudriere setup on HEAD r334236. 'poudriere testport -

Re: How to debug this...

On 26/05/2018 21:23, Adam Weinberger wrote: > On Sat, May 26, 2018 at 2:17 PM Matthew Seaman <matt...@freebsd.org> wrote: > >> On 26/05/2018 15:58, Adam Weinberger wrote: >>> On Sat, May 26, 2018 at 5:20 AM Matthew Seaman <matt...@freebsd.org> > wrote:

Re: How to debug this...

On 26/05/2018 15:58, Adam Weinberger wrote: > On Sat, May 26, 2018 at 5:20 AM Matthew Seaman <matt...@freebsd.org> wrote: > >> Hi, Folks, > >> Here's something that's had me head-scratching for a while. I've what >> should be a pretty routine update to sysutils

How to debug this...

Hi, Folks, Here's something that's had me head-scratching for a while. I've what should be a pretty routine update to sysutils/rsyslog8 in the works, except that my test builds in poudriere all bomb out with: === make: don't know how to make

Re: sysutils/ansible and FLAVOR (Python 3.6 support)

On 15/05/2018 08:02, Christopher Hall wrote: Hello everyone, I am looking at which is the best way to modify the sysutils/ansible port so that it will use Python3.6. Currently it has the "noflavors" option in the USE_PYTHON line son only a single packages with Python2.7 exists in the pkg repo.

Re: Updating www/py-recaptcha

On 22/04/2018 22:14, Dan Mahoney (Gushi) wrote: > 2) I can't figure out how to tell what packages (if any) depend on this > -- I know how to do it with *installed* packages, but not *all packages > total*, so I know who to reach out to for having them update.  Can > someone clue me in? cd

Re: pkg version - Orphanned status phpMyAdmin 4.7.9

On 07/04/2018 15:40, Jos Chrispijn wrote: > [Nub on ports] > > Running 'pkg version', I got phpMyAdmin status "?" (orphan) > > I first tried reinstalling the port, resulting in an error. > -- cut -- > > ===>  Installing for phpMyAdmin-php56-4.7.9 > > ===>   Registering installation for

Re: phpLDAPadmin -- is it time to drop this from ports?

On 05/04/2018 13:35, Per olof Ljungmark wrote: Quoting Matthew Seaman <matt...@freebsd.org>: Dear all, I've maintained the net/phpldapadmin port for _many_ years. Unfortunately this project seems to have ceased development upstream. There hasn't been a new release for more than 5

phpLDAPadmin -- is it time to drop this from ports?

Dear all, I've maintained the net/phpldapadmin port for _many_ years. Unfortunately this project seems to have ceased development upstream. There hasn't been a new release for more than 5 years, nor any sign of life from the original developer over much the same timespan. PLA still just

Re: Two pkg(8) repo configs pointing to same repo

On 27/03/2018 13:56, Anthony Jenkins via freebsd-ports wrote: Is there a way to configure a pkg(8) repo such that it has multiple ways to refer to the same physical repository?  I'm picturing the "url:" parameter being either a string or a list of strings: That isn't possible with pkg(8) at

Re: Error 8192 with phpldapadmin

On 08/02/2018 11:44, Carmel NY wrote: In any case, perhaps it is time to mark this port broken or state that it does not work with newer versions of PHP. Just a thought, but it might save someone a lot of wasted time. Yeah -- I'll mark the port as incompatible with php 7.2+ Cheers,

Re: Error 8192 with phpldapadmin

On 07/02/2018 21:09, Carmel NY wrote: > Name : phpldapadmin > Version: 1.2.3_7,1 > > Name : php72 > Version: 7.2.2 > > > Recently, "phpldapadmin" has started throwing an error message as > shown below: > > Unrecognized error number: 8192: Function

Re: Package depending on any one of multiple FLAVORS

On 06/02/2018 10:43, Dan Mahoney (Gushi) wrote: On Tue, 6 Feb 2018, Matthew Seaman wrote: This is down to a deficiency in pkg(8) -- it can't handle having a number of alternate packages or ranges of different package versions to fulfil a dependency.  The dependencies "baked into" ea

Re: Package depending on any one of multiple FLAVORS

On 06/02/2018 09:51, Ondra Knezour wrote: > Hi gang, > > documentation is little sparse yet (found only mention in the Porters > handbook, created PR for "end user" doc) and I am unsure, if we can > handle this. Best way I can describe my question is probably via > examples, so consider

Re: rubygem-facter versus sysutils/facter

On 06/02/2018 04:09, Dan Mahoney (Gushi) wrote: > In the meantime, I am actually curious about the questions I asked, as > they're more than this issue -- if specifying a binary name in a ports > Makefile will survive through to pkg.  (The docs say nothing one way or > the other), or how to get

Re: When does a newly committed port become installable via 'pkg'?

On 28/01/2018 20:14, James E Keenan wrote: > Earlier today (about 0910 EST), thanks to Po-Chuan Hsieh, a new port I > had created was committed to the repository.  It was very quickly > visible at these locations: > > https://svnweb.freebsd.org/ports/head/devel/p5-CPAN-Testers-Common-Client/ >

Re: daily security run output and joomla3

On 28/01/2018 18:04, Larry Rosenman wrote: > On Mon, Jan 29, 2018 at 02:56:51AM +0900, Yasuhiro KIMURA wrote: >> From: Carmel NY >> Subject: Re: daily security run output and joomla3 >> Date: Sun, 28 Jan 2018 17:38:10 + >> You can try "pkg check -r", see man

Re: Can we have multiple flavors for a port?

On 16/12/2017 14:24, Stefan Esser wrote: > Am 16.12.17 um 14:51 schrieb Matthew Seaman: >> >> I have a review up to add a USES=django -- >> https://reviews.freebsd.org/D12592 which I'm now modifying to be FLAVORS >> compatible given that has hit the tree. >> >

Can we have multiple flavors for a port?

I have a review up to add a USES=django -- https://reviews.freebsd.org/D12592 which I'm now modifying to be FLAVORS compatible given that has hit the tree. Now, we currently have ports for 4 different versions of django (1.8, 1.10, 1.11, 2.0) and the obvious next move is to add django-based

Re: Procmail Vulnerabilities check

On 09/12/2017 04:12, Dave Horsfall wrote: > On Fri, 8 Dec 2017, Steve Kargl wrote: > >> https://lists.freebsd.org/pipermail/freebsd-arch/2017-December/018712.html >> > > Well, I saw no reason to subscribe to freebsd-arch (I'm on enough lists > as it is)...  Are there any other lists that we

Re: Package database problems

On 16/11/2017 19:58, Paul Schmehl wrote: > --On November 16, 2017 at 8:49:24 PM +0100 Kurt Jaeger > wrote: > >> Hi! >> >>> > ???There's nothing to iterate over.  There's nothing in /var/db/pkg >>> > anymore except the SQLite databases. >>> >>> Then what is all this? (I'm only

Re: how to code Makefile to add script to periodic/daily

On 14/11/2017 23:24, Ernie Luzar wrote: > Searched the porters handbook and can not find any info about how to > code the Makefile for adding a file to /usr/local/etc/periodic/daily > directory. Was hoping for a canned macro but no joy. > > Can someone please point me to documentation or provide

Re: build logs

On 10/11/2017 14:44, blubee blubeeme wrote: > Is there a standard way to keep those make logs? Use poudriere. You'ld be able to access your build output via the web interface. Cheers, Matthew ___ freebsd-ports@freebsd.org mailing list

Re: cython 0.14

On 04/11/2017 13:41, blubee blubeeme wrote: > I have a port that needs cython 0.14 and not cython 0.26 > > I tried all sorts of things but this; > BUILD_DEPENDS= cython=0.14:lang/cython3 > > always returns that cython 0.14 isn't found, cython 0.24 is available but > my port won't build with

Fwd: [exp - 103i386-default-build-as-user][mail/sa-utils] Failed for sa-utils-0.04 in run-depends

Hmmm This nastygram from pkg-fallout arrived overnight. However, as far as I can tell, this is complaining about mail/spamassassin packages being broken, rather than any problem with mail/sa-utils itself. However, having checked the Build URL, poudriere seems to think spamassassin built

Re: New pkg audit FNs

On 09/10/2017 16:57, Roger Marquis wrote: > The reason I ask is CVE-2017-12617 was announced almost a week ago yet > there's no mention of it in the vulnerability database  The tomcat8 > port's Makefile also still points to the older, vulnerable version. > Tomcat is one of those popular,

Re: portmaster, portupgrade, etc

On 06/10/2017 00:29, tech-lists wrote: > On Thu, Oct 05, 2017 at 12:22:30PM +0100, Mike Clarke wrote: > >> the currently available package is built against php56. Using >> poudriere for this one task would >> be equivalent to using a steamroller to crack a peanut. Building >> phpMyAdmin from

Re: ABI confusion: freebsd:12:x86:64 or ABI: freebsd:12:amd64?

On 03/10/2017 12:08, Kurt Jaeger wrote: > Hi! > >> When using "poudriere", it seems ABI is freebsd:12:x86:64. > > Where do you get that value from ? If I access a repo, > I access e.g. > > https://repo.opsec.eu/${ABI} > > and ABI maps to > > FreeBSD:12:amd64 > There's history here.

Re: Status of portupgrade and portmaster?

On 02/10/2017 19:58, Marco Beishuizen wrote: > On Mon, 2 Oct 2017, the wise Matt Smith wrote: > >>> I'm running 11.1-STABLE now, upgrading every few months or when there >>> is an important security fix. Do I have to build a new system twice >>> in that case (once my running system and once the

Re: Status of portupgrade and portmaster?

On 30/09/2017 18:06, Kevin Oberman wrote: > John did state that he would continue to support synth. I can't say if he > has continued to make contributions. In any case, only poudriere is > available for maintaining ports in HEAD and I, for one, feel that it is > simply unacceptable as it make

Re: [HEADUP] FLAVORS landing.

On 28/09/2017 07:55, Stefan Esser wrote: > The matching of versions of base package and sub-packages must be > more strict than by version number, since trivial changes might be > applied to a port without incrementing the PORTREVISION, but with > impact on the binary, e.g. if the port is to built

Re: [HEADUP] FLAVORS landing.

On 27/09/2017 08:09, Tilman Keskinöz wrote: > > > On 2017-09-27 08:29, Matthew Seaman wrote: >> On 27/09/2017 07:11, Julian Elischer wrote: >>> Is there a document/paper on what this is and what it's limits are etc? >> >> https://wiki.freebsd.org/

Re: [HEADUP] FLAVORS landing.

On 27/09/2017 07:11, Julian Elischer wrote: > Is there a document/paper on what this is and what it's limits are etc? https://wiki.freebsd.org/Ports/FlavorsAndSubPackages https://wiki.freebsd.org/Ports/FlavorsMigration Cheers, Matthew signature.asc Description: OpenPGP

Re: Question: How to add a configuration file with autoplist ?

On 25/09/2017 12:10, Chris Rees wrote: > It's probably harmless to have a file listed twice, Listing a file twice will get you nasty-grams from the package build systems. Cheers, Matthew signature.asc Description: OpenPGP digital signature

Re: Installing ports in other places

On 22/09/2017 20:55, Paul Schmehl wrote: > I need to install mediawiki, but I want to install it in a different > location - in my home directory in a directory named wiki. > > I've read about DESTDIR, but I'm not certain that will work as I intend. > If I run make install DESTDIR=/homedir/wiki,

Re: What is the right way to make OPTIONS_DEFAULT depend on

On 03/09/2017 05:57, Yuri wrote: > This doesn't work: > >> .include >> >> .if ${OPSYS} == FreeBSD && ${OSVERSION} < 110 >> OPTIONS_DEFAULT+= MYOPT >> .endif > MYOPT isn't picked up > > > I tried with a regular expressions, witout .include: >> SYSVERSION=    ${OPSYS}${OSVERSION} >>

Re: pkg issue after FreeBSD 11 upgrade

On 10/08/2017 22:05, Cassiano Peixoto wrote: > I ran into an issue after FreeBSD 11 upgrade. I have some meta ports that > starts services like slapd. > > Its has been working fine on 10-STABLE. But after FreeBSD > 11-STABLE r321625M upgrade it stopped working. > > Here is a simple example of my

Re: FreeBSD Port: haproxy-1.7.8

On 10/08/2017 15:29, Alan Makoev via freebsd-ports wrote: > Hello FreeBSD team! > I installed haproxy and found that it's rc script ignores pidfile set in > rc.d. I suppose this is because these lines: > > : ${haproxy_enable:="NO"} > : ${haproxy_config:="%%PREFIX%%/etc/${name}.conf"} >

Re: packagesite.txz: Not Found

On 21/07/2017 04:00, @lbutlr wrote: > # cat /usr/local/etc/pkg/repos/FreeBSD.conf > FreeBSD: { > url: "pkg+http://pkg.FreeBSD.org//latest; This should be: url: pkg+http://pkg.FreeBSD.org/${ABI}/latest Cheers, Matthew signature.asc Description: OpenPGP digital

Re: FW: build for py27-sispy-1.0.1 in patch

On 2017/07/13 14:02, Miller, Vincent (Rick) via freebsd-ports wrote: > A new port request (PR #219823) for py-sispy, of which I am > maintainer, was recently committed to ports’ HEAD though the code > committed differs slightly from the code submitted in that sources > are pulled from CHEESESHOP

Re: LIB_DEPENDS with option?

On 2017/07/07 09:57, Johannes Lundberg wrote: > Hi > > Is there anyway to specify a LIB_DEPENDS with an option? > > ie. > > LIB_DEPENDS= libwayland-egl.so:graphics/mesa-libs(WAYLAND=on) > Traditionally the way to do this is to create a slave port of the library which enforces the desired

Re: undefined reference to `kevent@FBSD_1.5'

On 2017/07/06 11:22, Otacílio wrote: > After a recent partial ports update in FreeBSD 12 r318838 AMD64 I'm > getting some errors when rebuilding ports with this message: > > undefined reference to `kevent@FBSD_1.5' > > Can anyone give a tip on what is causing this? > This is a versioned

Re: [RFC] Why FreeBSD ports should have branches by OS version

On 06/23/17 09:47, demelier.da...@gmail.com wrote: > On Thu, 2017-06-22 at 16:11 -0500, Mark Linimon wrote: >> On Thu, Jun 22, 2017 at 12:32:45PM -0400, scratch65...@att.net wrote: >>> My problem is that my industry experience tells me that reducing >>> the frequency of port releases is

Re: [RFC] Why FreeBSD ports should have branches by OS version

On 2017/06/22 20:56, Baho Utot wrote: > One could still use releng 11.0 ports with 10.3 OS could they not No, not in general. You've got it the wrong way round. You might get away with releng 10.3 ports and 11.0 OS for a while but it will likely cause you grief when you do run afoul of a

Re: [RFC] Why FreeBSD ports should have branches by OS version

On 2017/06/22 15:03, scratch65...@att.net wrote: > Why don't the same choices apply here? What am I missing? Two things: 1) It's progress in the development of the FreeBSD base system that drives the release cycle. The general state of the ports does not exert much influence on release

Re: pkg convert?

On 19/06/2017 01:04, Thomas Mueller wrote: > Looking through the man page for pkg, I see there is still an entry for > convert ("pkg help convert" or "man pkg-convert"). > > DESCRIPTION > pkg convert is used to convert from/to pkg(8) local database to legacy > pkg_install tools format.

Re: bapt@ back on portmgr

On 09/06/2017 00:54, Thomas Mueller wrote: > from René Ladan: > >> it is our pleasure to announce that Baptiste Daroussin (bapt@) is >> back on portmgr.> > Is this a new port in the works, or is portmgr a (confusing) > abbreviation for portmanager? No, portmgr is the group of people that

Re: Naming convention for etc/periodic/*/* files?

On 07/06/2017 16:18, Christian Weisgerber wrote: > What is the naming convention for etc/periodic/*/* files installed > by ports? > > Looking over the ports tree, I see that most adhere to the > NNN.*name* pattern also used in the base system, although it's > unclear how the NNN numbers are

Re: wget 1.19 missed IRI supporting

On 06/06/2017 10:37, Cos Chan wrote: > I got mistake while running this command: > > wget --no-verbose --remote-encoding=UTF-8 --local-encoding=UTF-8 --mirror > --directory-prefix=/foo/ --no-parent --no-host-directories --cut-dirs=2 > --force-directories --accept=*.pdf

Re: Pass options to dependency

On 05/06/2017 10:56, Eugene Grosbein wrote: > How can a port (its Makefile) pass a build option to BUILD_DEPENDS? > For example, devel/ragel has: > > DOCS_USE= TEX=latex:build > DOCS_BUILD_DEPENDS= fig2dev:print/transfig > > And "make -C /usr/ports/devel/ragel all-depends-list"

Re: Finding depends-on ports

On 02/06/2017 20:18, Beeblebrox via freebsd-ports wrote: > I'm running a default-settings ports build from a ports-list file in > poudriere (-f /path/file), which means no options have been defined by > "# make config" or by make.conf (empty /var/db/ports, so can't look > there). > > Is there an

Re: The future of portmaster [and of ports-mgmt/synth]

On 2017/05/31 17:11, Roger Marquis wrote: > Mark Linimon wrote: >> * some extensive changes to the ports framework are coming; > > Is there a URL (other than svnweb) where we can see a project plan for > these changes? As in the recent past (i.e., since 8-REL) the FreeBSD > end-user community

Re: Recoll version bump in ports

On 2017/05/23 15:58, Jim Ohlstein wrote: > > > On 05/23/2017 10:54 AM, Matthew Seaman wrote: >> On 2017/05/23 15:38, Michael L. Wilson wrote: >>> Now, I do happen to know what filters/rclpdf is and what it does. But in >>> this case I am not sure what mak

Re: Recoll version bump in ports

On 2017/05/23 15:38, Michael L. Wilson wrote: > Now, I do happen to know what filters/rclpdf is and what it does. But in > this case I am not sure what make is asking for or how to proceed to > step. I could potentially accomplish this with some walk through. filters/rclpdf is a run- or build-

Re: How should we name node-js ports ?

On 20/05/2017 07:56, Julian Elischer wrote: > this brings up the whole question of whether we should package these > things ourselves anyhow. > python and perl have their own schemes (pip et al.) and with npm (and > others) node is no exception. > it seems that to chase these packages down

  1   2   3   4   5   6   7   8   9   >