Matthieu Volat wrote:
> I've been continuing to maintain my gimp 2.8 experimental ports, more
> rigorously checking pkg-plist files and updating to 2.8.2 (well, just
> incrementing the version number in the Makefile).
>
> For those who are interested, until gimp 2.8 is properly imported in
> the p
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common probl
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common probl
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port, inclu
===>>> Upgrade of apr-ipv6-devrandom-1.4.5.1.3.12_1 to apr-1.4.6.1.4.1_1
succeeded
# svn status /usrp
Shared object "libaprutil-1.so.3" not found, required by "svn"
Perhaps subversion version should be bumped too?
Anton
___
freebsd-ports@freebsd.org m
The development of FreeBSD ports is done in Subversion nowadays.
For the sake of compatibility a Subversion to CVS exporter is
in place which has some limitations. For CVSup mirroring cvsup
based on Ezm3 is used which breaks regularly especially on amd64
and with Clang and becomes more and more unm
[ Beat Gaetzi wrote on Fri 7.Sep'12 at 14:36:32 +0200 ]
> % svn co https://svn0.us-west.FreeBSD.org/ports/head /usr/ports
>
> and update a checked out repository using:
>
> % cd /usr/ports && svn update
>
Can I just ask something about changing over to use sv - should I delete
the entire /usr
On 07/09/2012 14:36, Beat Gaetzi wrote:
> For those reasons by February 28th 2013 the FreeBSD ports tree will
> no longer be exported to CVS. Therefore ports tree updates via CVS
> or CVSup will no longer available after that date. All users who use
> CVS or CVSup to update the ports tree are enco
On 09/07/12 13:18, Ivan Voras wrote:
> On 07/09/2012 14:36, Beat Gaetzi wrote:
>
>> For those reasons by February 28th 2013 the FreeBSD ports tree will
>> no longer be exported to CVS. Therefore ports tree updates via CVS
>> or CVSup will no longer available after that date. All users who use
>> C
On 7 Sep 2012 12:20, "Ivan Voras" wrote:
>
> On 07/09/2012 14:36, Beat Gaetzi wrote:
>
> > For those reasons by February 28th 2013 the FreeBSD ports tree will
> > no longer be exported to CVS. Therefore ports tree updates via CVS
> > or CVSup will no longer available after that date. All users who
On Fri, Sep 07, 2012 at 11:53:47AM +0100, Jamie Paul Griffin wrote:
> ...
> Can I just ask something about changing over to use sv - should I delete
> the entire /usr/ports tree before I use :
>
> svn co https://svn0.us-west.FreeBSD.org/ports/head /usr/ports
You might want to consider saving
Moved discussion to freebsd-ports...
- Original Message -
From: "Beat Gaetzi"
portsnap also doesn't appear to provide feature compatibility
with csup, specifically it states in the man page that it
deletes unknown files and restore modified files to their
unmodified state.
This makes
textproc/groff is more up to date and
more complete than the src version,
for obvious reasons. I use groff for
document preparation, so need the ports
version. I don't mind having the two
versions, just have to remember to use
-M man switch, or set the PATH accordingly.
However, I wonder, with all
From owner-freebsd-po...@freebsd.org Fri Sep 7 13:04:28 2012
> svn co https://svn0.us-west.FreeBSD.org/ports/head /usr/ports
I've got svn://svn.freebsd.org/ports/head
Is that no nonger valid?
Seems to work though.
Anton
___
freebsd
Hi!
> > Can I just ask something about changing over to use sv - should I delete
> > the entire /usr/ports tree before I use :
> >
> > svn co https://svn0.us-west.FreeBSD.org/ports/head /usr/ports
>
> You might want to consider saving away /usr/ports/distfiles and/or
> /usr/ports/packages fi
On 7 September 2012 08:16, Kurt Jaeger wrote:
> What happens, if one does:
>
> svn update
>
> and then adds some files to distfiles/
>
> and then does some
>
> svn update
>
> again. Will the distfiles be deleted ? Ignored ? ... ?
ignored.
--
Eitan Adler
On 07-09-2012 13:04, Anton Shterenlikht wrote:
> However, I wonder, with all the talk
> about some tools better kept in ports
> rather than in base (e.g. pkg), is it
> perhaps better to remove groff from
> base completely?
We've been discussing replacing groff with mdocml for quite some time. Chec
,--- Beat Gaetzi (Fri, 07 Sep 2012 14:36:32 +0200) *
| All users who use CVS or CVSup to update the ports tree are
| encouraged to switch to portsnap(8) [1] or for users which need more
| control over their ports collection checkout use Subversion directly
I just switched to 'svn'-ports on an
On 7 September 2012 08:30, Alex Goncharov wrote:
> I know I can copy it from one of my existing systems but what's the
> official vision for this first step? portsnap?
pkg or portsnap.
> I assume this is no longer possible, right?
It is possible to do with portsnap REFUSE lines. It is also pos
On Fri, 7 Sep 2012 08:23:16 -0400
Eitan Adler wrote:
> On 7 September 2012 08:16, Kurt Jaeger wrote:
> > What happens, if one does:
> >
> > svn update
> >
> > and then adds some files to distfiles/
> >
> > and then does some
> >
> > svn update
> >
> > again. Will the distfiles be deleted ? Ignor
On 7 September 2012 08:43, Sergey V. Dyatko wrote:
> On Fri, 7 Sep 2012 08:23:16 -0400
> Eitan Adler wrote:
> what about svn st[atus] ?:)
svn update and svn status are different. I'd suggest you try this one
for yourself.
--
Eitan Adler
___
freebsd
on 07/09/2012 14:57 Steven Hartland said the following:
> Is there no way to tell it not to delete unknown files so we
> don't have to add addional steps to the workflow flow of adding
> additional patches to local port builds?
I would hazard a recommendation to use something like git-svn / svk /e
Dnia 2012-09-07, o godz. 12:57:42
"Steven Hartland" napisał(a):
>Is there no way to tell it not to delete unknown files so we
>don't have to add addional steps to the workflow flow of adding
>additional patches to local port builds?
>
>I appreciate things must move forward but this seems like a s
On Fri, 7 Sep 2012, Beat Gaetzi wrote:
The development of FreeBSD ports is done in Subversion nowadays.
For the sake of compatibility a Subversion to CVS exporter is
in place which has some limitations. For CVSup mirroring cvsup
based on Ezm3 is used which breaks regularly especially on amd64
an
On 7 Sep 2012 15:39, "Pawel Pekala" wrote:
>
> Dnia 2012-09-07, o godz. 12:57:42
> "Steven Hartland" napisał(a):
>
> >Is there no way to tell it not to delete unknown files so we
> >don't have to add addional steps to the workflow flow of adding
> >additional patches to local port builds?
> >
> >
Thought I would let you know...
This seems to have broken the build...
===> libpkg (all)
Warning: Object directory not changed from original
/exports/pkgng/libpkg
cc -O2 -pipe -march=native -DHAVE_GRUTILS -std=c99
-I/exports/pkgng/libpkg -I/exports/pkgng/libpkg/../external/sqlite
-I/exports/pkg
27 matches
Mail list logo
