Mathieu Arnold wrote on 11/07/2017 18:03:
Le 07/11/2017 à 16:54, Miroslav Lachman a écrit :
What is the best way to maintain local ports tree changes?
I am building packages in poudriere, 4 different sets for 2 archs (8
sets in total).
I have some local ports and some changes to official
Le 07/11/2017 à 16:54, Miroslav Lachman a écrit :
> What is the best way to maintain local ports tree changes?
>
> I am building packages in poudriere, 4 different sets for 2 archs (8
> sets in total).
>
> I have some local ports and some changes to official ports. Now we are
&g
On 11/07/2017 07:54, Miroslav Lachman wrote:
What is the best way to maintain local ports tree changes?
I am building packages in poudriere, 4 different sets for 2 archs (8
sets in total).
I have some local ports and some changes to official ports. Now we are
planing to do some small
What is the best way to maintain local ports tree changes?
I am building packages in poudriere, 4 different sets for 2 archs (8
sets in total).
I have some local ports and some changes to official ports. Now we are
planing to do some small changes in ports/Mk too.
So what is the best way to
t... what is the right way of setting this up (I have a
> local cvsup repo)?
I have several local ports, to set up which I found the following
useful:
1. Vivek Khera, `Making a local branch of the ports tree',
http://lists.freebsd.org/pipermail/freebsd-ports/2007-April/040366.html
2. Rand
On Fri, 03 Jul 2009, Aryeh M. Friedman wrote:
> Note: If I am the unofficial co-maintainer of a port (devel/aegis) [i.e.
> it was added at my request by the maintainer because at the time I
> didn't know how to make a proper port and have the email transcript to
> prove it) and my co-maintai
My site has a number of tools we have written for internal use only and
want to make it so all one has to do to set a new machine up with these
tools and the standard ports needed is rune portmaster on our local
meta-port... what is the right way of setting this up (I have a local
cvsup repo)?
Walter Ian Kaye wrote:
At 11:10 a -0800 05/11/2007, Beech Rintoul didst inscribe upon an
electronic papyrus:
Walter Ian Kaye wrote:
Hi,
Locally I see this:
/usr/ports/www/lynx-ssl> pkg_version -v
[...]
lynx-ssl-2.8.5_2= up-to-date with port
But freebsd.org website sh
On Fri, May 11, 2007 at 01:08:53PM -0700, Walter Ian Kaye wrote:
> At 11:10 a -0800 05/11/2007, Beech Rintoul didst inscribe upon an
> electronic papyrus:
>
> >Walter Ian Kaye wrote:
> >>Hi,
> >>
> >>Locally I see this:
> >>
> >>/usr/ports/www/lynx-ssl> pkg_version -v
> >>[...]
> >>lynx-ssl-2.8.5
At 11:10 a -0800 05/11/2007, Beech Rintoul didst inscribe upon an
electronic papyrus:
Walter Ian Kaye wrote:
Hi,
Locally I see this:
/usr/ports/www/lynx-ssl> pkg_version -v
[...]
lynx-ssl-2.8.5_2= up-to-date with port
But freebsd.org website shows 2.8.6_4,1
How do I
Walter Ian Kaye wrote:
Hi,
Locally I see this:
/usr/ports/www/lynx-ssl> pkg_version -v
[...]
lynx-ssl-2.8.5_2= up-to-date with port
But freebsd.org website shows 2.8.6_4,1
How do I get my ports to know what's actually available?
thanks,
-Walter
running os version 4.10
On Fri, May 11, 2007 at 11:24:48AM -0700, Walter Ian Kaye wrote:
> Hi,
>
> Locally I see this:
>
> /usr/ports/www/lynx-ssl> pkg_version -v
> [...]
> lynx-ssl-2.8.5_2= up-to-date with port
>
>
> But freebsd.org website shows 2.8.6_4,1
>
> How do I get my ports to know what
Hi,
Locally I see this:
/usr/ports/www/lynx-ssl> pkg_version -v
[...]
lynx-ssl-2.8.5_2= up-to-date with port
But freebsd.org website shows 2.8.6_4,1
How do I get my ports to know what's actually available?
thanks,
-Walter
running os version 4.10
___
On Tue, 10 Apr 2007 01:13:29 -0500, Vulpes Velox <[EMAIL PROTECTED]>
wrote:
I was just wondering what any one else thought of the idea of adding
a local directory to the ports tree and to the .cvsignore. This would
be a directory for users to put local custom ports.
I have my own ports tree
ht be a different story,
> not sure how it handles updates...
Just fine. The author even added the -l option at my request so you can
still use portsnap's INDEX updating stuff. You just need to collect
the results of "make describe" in your local ports and pass the file
con
On Tue, 10 Apr 2007 21:15:04 -0500
Josh Paetzel <[EMAIL PROTECTED]> wrote:
> Vulpes Velox wrote:
> > I was just wondering what any one else thought of the idea of
> > adding a local directory to the ports tree and to the .cvsignore.
> > This would be a directory for users to put local custom ports
Vulpes Velox wrote:
> I was just wondering what any one else thought of the idea of adding
> a local directory to the ports tree and to the .cvsignore. This would
> be a directory for users to put local custom ports.
There's nothing to stop you from creating /usr/ports/local right now
and just us
I was just wondering what any one else thought of the idea of adding
a local directory to the ports tree and to the .cvsignore. This would
be a directory for users to put local custom ports.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.
On Thu, 15 Feb 2007 15:54:29 -0600, Doug Barton <[EMAIL PROTECTED]> wrote:
David Gilbert wrote:
"Jeremy" == Jeremy Messenger <[EMAIL PROTECTED]> writes:
Jeremy> Give ports-mgmt/portmaster a try.
I just did. One flaw it has is that I have two no longer supported
ports installed.
What do yo
David Gilbert wrote:
>> "Jeremy" == Jeremy Messenger <[EMAIL PROTECTED]> writes:
>
> Jeremy> Give ports-mgmt/portmaster a try.
>
> I just did. One flaw it has is that I have two no longer supported
> ports installed.
What do you mean by "no longer supported?"
> I want to run portmaster -a
/makefile.inc
$ echo "PKGNAMESUFFIX?=-local" >> /usr/ports/LOCAL/makefile.inc
I found a way where you don't need to set PKGCATEGORY, and allows your
local ports to be included in a 'make index'.
/usr/ports/Makefile.local
# $FreeBSD$
#
SUBDIR+=local
/usr/ports/loc
Hallo Charles Sprickman,
> I'm finding that there are a number of ports that we need to patch for
> some functionality that's unique to our business (qmail, mailfront, etc.).
> Currently we just do "make patch" and then apply our patches. This works,
> but is a bit of a pain to maintain.
> Is
Matthew Seaman wrote:
> That's a generic problem with ports -- instead of registering a
> dependency on the package that provided the file that satisfied the
> test specified by the FOO_DEPENDS variable in the port Makefile, the
> dependency is registered on the default package to install to resol
Charles,
On Nov 3, 2006, at 3:30 PM, Charles Sprickman wrote:
Hello all,
I'm finding that there are a number of ports that we need to patch
for some functionality that's unique to our business (qmail,
mailfront, etc.). Currently we just do "make patch" and then apply
our patches. This w
On Fri, Nov 03, 2006 at 03:30:47PM -0500, Charles Sprickman wrote:
> I'm finding that there are a number of ports that we need to patch for
> some functionality that's unique to our business (qmail, mailfront, etc.).
> Currently we just do "make patch" and then apply our patches. This works,
>
list, for my message with
subject "Re: category for local ports".
I only use it for truly local ports, not altered versions of regular
ports. Can you not submit patches to them with appropriate flags to
set to get the behavior you desire?
Beyond that, I have a few other questi
Charles Sprickman wrote:
> Is there a way to create a "local" category? ie: /usr/ports/LOCAL
Create /usr/ports/Makefile.local containing:
SUBDIR+= LOCAL
> -By default cvsup and (I assume portsnap) would nuke anything in
> /usr/ports that was not part of the main ports tree. How can this be
You've got a bunch of misconceptions. In this case, that turns out to
be good, because the solutions are a lot simpler than you think.
Charles Sprickman <[EMAIL PROTECTED]> writes:
> Hello all,
>
> I'm finding that there are a number of ports that we need to patch for
> some functionality that's
Hello all,
I'm finding that there are a number of ports that we need to patch for
some functionality that's unique to our business (qmail, mailfront, etc.).
Currently we just do "make patch" and then apply our patches. This works,
but is a bit of a pain to maintain.
Is there a way to create
29 matches
Mail list logo
