Re: poudriere with custom packages

On 16/07/2015 04:49, Aristedes Maniatis wrote: > I have a custom built package which I'm building outside the FreeBSD > ports system (using pkg-create commands). How can I add that package > to a poudriere managed repository so that it appears in the package > index and can be easily installed like

Re: www/squid's cache dir

Hi Nick! > FWIW, I have the squid port installed on hundreds of systems, however I do > not use the port defaults and have logs and cache on a separate filesystem > mounted in /squid (i.e., /squid/logs, /squid/cache). In my opinion, it > makes sense for the port to default to using /var/squid/c

Re: poudriere with custom packages

On Thu, 16 Jul 2015 08:09:39 +0100 Matthew Seaman wrote: > On 16/07/2015 04:49, Aristedes Maniatis wrote: > > I have a custom built package which I'm building outside the FreeBSD > > ports system (using pkg-create commands). How can I add that package > > to a poudriere managed repository so that

Re: poudriere with custom packages

> Matthew Seaman wrote: > >> I'd be interested to hear about how you are creating packages outside >> the ports tree. This is something we'd like to facilitate, but at the >> moment pkg(8) and the ports are deeply entwined and there isn't much >> useable documentation or prior art for how to do

Re: poudriere with custom packages

On 07/16/15 10:19, Aristedes Maniatis wrote: > It was pretty much magic, but I pulled apart some existing packages > and took a guess at most of it. > >https://gist.github.com/ari/01eaae67d8c941ccaf68 > > On the plus side this is a really simple package, nothing > complicated. Install a coupl

Re: poudriere with custom packages

Matthew Seaman wrote: > On 16/07/2015 04:49, Aristedes Maniatis wrote: > >> I have a custom built package which I'm building outside the FreeBSD >> ports system (using pkg-create commands). How can I add that package >> to a poudriere managed repository so that it appears in the package >> index

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

Re: poudriere with custom packages

Michelle Sullivan wrote: > >> >> >> > You need "CATEGORIES += myports" (or something similar) as well... > > Michelle > > Sorry I'm talking out of my butt you can add a "local" top level add add it with "CATEGORIES += local" and then add a makefile as Matthew indicated (without the

port renaming

Port maintainers and port commiters, when PORTNAME/PKGNAMEPREFIX/PKGNAMESUFFIX is changed, please note this change in commit log and for important ports also in /usr/ports/UPDATING. Any rename affect at leas some of FreeBSD users and Depends in our local ports was broken and I spent some time t

Re: port renaming

On Thu, Jul 16, 2015 at 2:56 PM, Anton Yuzhaninov wrote: > > Port maintainers and port commiters, when > PORTNAME/PKGNAMEPREFIX/PKGNAMESUFFIX is changed, please note this change in > commit log and for important ports also in /usr/ports/UPDATING. Any rename > affect at leas some of FreeBSD user

Re: www/squid's cache dir

On Thu, Jul 16, 2015 at 1:05 AM, timp wrote: > Hi Nick! > > > FWIW, I have the squid port installed on hundreds of systems, however I > do > > not use the port defaults and have logs and cache on a separate > filesystem > > mounted in /squid (i.e., /squid/logs, /squid/cache). In my opinion, it >

Re: port renaming

On Thu, Jul 16, 2015 at 7:04 AM, Vsevolod Stakhov wrote: > On Thu, Jul 16, 2015 at 2:56 PM, Anton Yuzhaninov > wrote: > > > > Port maintainers and port commiters, when > PORTNAME/PKGNAMEPREFIX/PKGNAMESUFFIX is changed, please note this change in > commit log and for important ports also in /usr/

Re: port renaming

On 07/16/15 20:11, Henry Hu wrote: On Thu, Jul 16, 2015 at 2:56 PM, Anton Yuzhaninov mailto:cit...@citrin.ru>> wrote: Port maintainers and port commiters, when PORTNAME/PKGNAMEPREFIX/PKGNAMESUFFIX is changed, please note this change in commit log and for important ports also in /usr/ports/UPDAT

Re: port renaming

On 16/07/2015 18:11, Henry Hu wrote: > > > On Thu, Jul 16, 2015 at 7:04 AM, Vsevolod Stakhov > mailto:vsevo...@highsecure.ru>> wrote: > > On Thu, Jul 16, 2015 at 2:56 PM, Anton Yuzhaninov > wrote: > > > > Port maintainers and port commiters, when > PORT

Re: port renaming

On Thu, Jul 16, 2015 at 8:23 PM, Vsevolod Stakhov wrote: > On 16/07/2015 18:11, Henry Hu wrote: >> >> >> On Thu, Jul 16, 2015 at 7:04 AM, Vsevolod Stakhov >> mailto:vsevo...@highsecure.ru>> wrote: >> >> On Thu, Jul 16, 2015 at 2:56 PM, Anton Yuzhaninov > > wrote: >

Re: port renaming

On 16/07/2015 18:32, Kimmo Paasiala wrote: > On Thu, Jul 16, 2015 at 8:23 PM, Vsevolod Stakhov > wrote: >> On 16/07/2015 18:11, Henry Hu wrote: >>> >>> >>> On Thu, Jul 16, 2015 at 7:04 AM, Vsevolod Stakhov >>> mailto:vsevo...@highsecure.ru>> wrote: >>> >>> On Thu, Jul 16, 2015 at 2:56 PM, Anto

Re: port renaming

On Thu, Jul 16, 2015 at 10:46 AM, Vsevolod Stakhov wrote: > On 16/07/2015 18:32, Kimmo Paasiala wrote: > > On Thu, Jul 16, 2015 at 8:23 PM, Vsevolod Stakhov > > wrote: > >> On 16/07/2015 18:11, Henry Hu wrote: > >>> > >>> > >>> On Thu, Jul 16, 2015 at 7:04 AM, Vsevolod Stakhov > >>> mailto:vsevo

Re: port renaming

On 16/07/2015 18:23, Vsevolod Stakhov wrote: > So the answer is no: we need a special field in manifests to make > renaming transparent for pkg and, in turn, for users. How is a renamed package significantly different to choosing between alternate packages that could fulfil a dependency? Doesn't

Re: Swat2

Swat isn't a part of Samba4 anymore. Looking at the dates in the GIT repository I'd say it's been given up(for good). Regards, Timur. On Tue, Jul 14, 2015 at 8:34 PM, Carmel NY wrote: > I understand that there is a "swat2" available for Samba4*. I have not seen > it in the ports system thought.

INDEX build failed for 8.x

INDEX build failed with errors: Generating INDEX-8 - please wait..--- describe.accessibility --- --- describe.arabic --- --- describe.archivers --- --- describe.astro --- --- describe.audio --- --- describe.benchmarks --- --- describe.biology --- --- describe.cad --- --- describe.chinese --- --- de

Re: port renaming

On Thu, Jul 16, 2015 at 06:23:03PM +0100, Vsevolod Stakhov wrote: > 3) many items are missing in MOVED (and I've recently missed one when > changing a port, for example) Please file PRs for missing entries. I have a portsmon page that attempts to correlated the category/Makefiles to MOVED and als

INDEX now builds successfully on 8.x

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

Re: poudriere with custom packages

On 16/07/2015 13:19, Aristedes Maniatis wrote: I have a custom built package which I'm building outside the FreeBSD ports system (using pkg-create commands). How can I add that package to a poudriere managed repository so that it appears in the package index and can be easily installed like any o

Re: poudriere with custom packages

On 17/07/2015 06:59, Shane Ambler wrote: > I recall hearing a plan to add a weight to repos to choose which is > used first. I have found so far that the last repo entry (they are all > listed in one config file) is used over others if the same port is in > multiple repos. This was added several r

Re: poudriere with custom packages

On 17/07/2015 3:59pm, Shane Ambler wrote: > As long as the name you use for the port is unique, steps like portsnap > or svn update should not remove it. I would still keep a copy elsewhere. Thanks for that. I'm doing exactly what everyone here suggests (abandoning my reversing engineered +MANIFE