On Fri, Jun 15, 2012 at 12:04:52PM +, Baptiste Daroussin wrote:
> bapt2012-06-15 12:04:52 UTC
>
> FreeBSD ports repository
>
> Modified files:
> Mk bsd.port.mk
> Log:
> Fix sanity-config error when using WRKDIRPREFIX [1]
> While apply the same fix to f
On Fri, Jun 08, 2012 at 07:52:39PM +, Ryan Steinmetz wrote:
> zi 2012-06-08 19:52:39 UTC
>
> FreeBSD ports repository
>
> Modified files:
> Mk bsd.port.mk
> Log:
> Fix condition where _FILE_COMPLETE_OPTIONS_LIST is not defined (introduced
> by previous
On Wed, Jun 06, 2012 at 02:05:05PM -0700, Doug Barton wrote:
> I thank you for this change, and many confused portmaster users will
> thank you for it as well. :)
>
> Someday I'd like to revisit
> http://www.freebsd.org/cgi/query-pr.cgi?pr=106483. I still remain
> convinced that the best place to
I thank you for this change, and many confused portmaster users will
thank you for it as well. :)
Someday I'd like to revisit
http://www.freebsd.org/cgi/query-pr.cgi?pr=106483. I still remain
convinced that the best place to put this information is in /var/db/pkg,
not /var/db/ports. However I have
On Wed, 9 Nov 2011, Martin Wilke wrote:
> - Make WITH_FBSD10_FIX globally
> - Add a new flag WITHOUT_FBSD10_FIX for maintainer testing
>
> Some additional notes:
> We are planing to make 10 exp-run after the 9.0 Release within 2 weeks to
> poke maintainers
> and upstream as to ensure
On Sun, Sep 04, 2011 at 05:35:07PM +, Sunpoet Po-Chuan Hsieh wrote:
> sunpoet 2011-09-04 17:35:07 UTC
>
> FreeBSD ports repository
>
> Modified files:
> Mk bsd.port.mk bsd.python.mk
> Log:
> - Revert accidental commit
>
> Revision ChangesPath
> 1
* Baptiste Daroussin (b...@freebsd.org) wrote:
> bapt2011-06-06 05:53:51 UTC
>
> FreeBSD ports repository
>
> Modified files:
> Mk bsd.port.mk
> Log:
> - remove some old code (unsused on supported OS) [1]
> - prevent some useless external program call (bas
I think the following is a nice optimization, but I'm confused as to why
we need to check this at all:
check-categories:
.for cat in ${CATEGORIES}
- @if ${ECHO_CMD} ${VALID_CATEGORIES} | ${GREP} -wq ${cat}; then \
- ${TRUE}; \
- else \
- ${ECHO_MSG} "${PKGNAME}: Make
Yay! Hopefully some of the fetching errors reported by portmaster users
will be fixed by this change.
Doug
On 12/09/2010 12:33, Pav Lucistnik wrote:
pav 2010-12-09 20:33:02 UTC
FreeBSD ports repository
Modified files:
Mk bsd.port.mk
Log:
- Upgrade
On 2010/12/01 09:53, Max Brazhnikov wrote:
On Wed, 1 Dec 2010 08:32:50 + (UTC), Martin Wilke wrote:
miwi2010-12-01 08:32:50 UTC
FreeBSD ports repository
Modified files:
Mk bsd.port.mk
Log:
- Remove two checks obviated by the removal of _OPTIONSFIL
On Wed, 1 Dec 2010 08:32:50 + (UTC), Martin Wilke wrote:
> miwi2010-12-01 08:32:50 UTC
>
> FreeBSD ports repository
>
> Modified files:
> Mk bsd.port.mk
> Log:
> - Remove two checks obviated by the removal of _OPTIONSFILE in revision
> 1.596 [1] - Remove
On 4/16/2010 12:18 AM, Pav Lucistnik wrote:
> pav 2010-04-16 07:18:28 UTC
>
> FreeBSD ports repository
>
> Modified files:
> Mk bsd.port.mk
> Log:
> - Desupport RC_SUBR and RC_SUBR_SUFFIX macros, they have been replaced with
> literal "/etc/rc.subr" and
Erwin Lansing:
> Portmgr holds a hard lock on this file all the time, and especially
> during a freeze we cannot allow _any_ commit including whitespace. Do
> not ever do this again!
Understood.
--
Christian "naddy" Weisgerber na...@mips.inka.de
___
On Mon, Sep 21, 2009 at 09:37:04PM +0200, Christian Weisgerber wrote:
> Pav Lucistnik:
>
> > > Modified files:
> > > Mk bsd.port.mk
> > > Log:
> > > Format a few comment lines for ts=4 and <80 columns.
> > >
> > > Feature safe: yes
> >
> > Approved by... ?
>
>
On Mon, Sep 21, 2009 at 09:37:04PM +0200, Christian Weisgerber wrote:
> It's a _typo_ commit, fer chrissake.
IIRC changes to bsd.port.mk force rebuilds for people in tinderboxen?
mcl
___
cvs-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/
Pav Lucistnik:
> > Modified files:
> > Mk bsd.port.mk
> > Log:
> > Format a few comment lines for ts=4 and <80 columns.
> >
> > Feature safe: yes
>
> Approved by... ?
It's a _typo_ commit, fer chrissake.
> # DO NOT COMMIT CHANGES TO THIS FILE BY YOURSELF, EVE
> naddy 2009-09-21 19:13:51 UTC
>
> FreeBSD ports repository
>
> Modified files:
> Mk bsd.port.mk
> Log:
> Format a few comment lines for ts=4 and <80 columns.
>
> Feature safe: yes
Approved by... ?
# DO NOT COMMIT CHANGES TO THIS FILE BY YOURSELF, EV
The Restless Daemon identified a mtree error while trying to build:
ko-hanterm-3.1.6_3 maintained by c...@freebsd.org
Makefile ident: $FreeBSD: ports/korean/hanterm/Makefile,v 1.29 2009/06/09
15:33:12 amdmi3 Exp $
Excerpt from
http://QAT.TecNik93.com/logs/7-STABLE-FPT-NPD/ko-hanterm-3.1.6_3.lo
Stanislav Sedov píše v út 09. 06. 2009 v 19:47 +0400:
> On Tue, 09 Jun 2009 17:11:09 +0200
> Pav Lucistnik mentioned:
>
> > Stanislav Sedov píše v út 09. 06. 2009 v 19:06 +0400:
> >
> > > > - Fix COPYTREE_* macros not to change permissions and ownership on
> > > > files, that
> > > > were
On Tue, 09 Jun 2009 17:11:09 +0200
Pav Lucistnik mentioned:
> Stanislav Sedov píše v út 09. 06. 2009 v 19:06 +0400:
>
> > > - Fix COPYTREE_* macros not to change permissions and ownership on
> > > files, that
> > > were already present in the target path
> > >
> > > Submitted by: b
Stanislav Sedov píše v út 09. 06. 2009 v 19:06 +0400:
> > - Fix COPYTREE_* macros not to change permissions and ownership on files,
> > that
> > were already present in the target path
> >
> > Submitted by: beech
>
> This breaks a lot of ports at least on 7-STABLE. GNU CPIO changes
On Sun, 11 Jan 2009 11:04:05 + (UTC)
Pav Lucistnik mentioned:
> pav 2009-01-11 11:04:05 UTC
>
> FreeBSD ports repository
>
> Modified files:
> Mk bsd.port.mk
> Log:
> - Remove conditional checks and support for FreeBSD versions prior
> 6.0-RELEASE
>
On Sat, Jan 17, 2009 at 06:44:15PM +, Sergey Skvortsov wrote:
> skv 2009-01-17 18:44:15 UTC
>
> FreeBSD ports repository
>
> Modified files:
> Mk bsd.port.mk
> Log:
> Set PERL_VERSION and PERL_VER to "5.8.9".
Do we really need both of them?
./danfe
___
Alexander Leidinger píše v st 12. 03. 2008 v 11:46 +0100:
> > Only difference I see is that you condition the use of linux mdconfig by
> > presence of USE_LINUX, I need USE_LINUX_PREFIX, which is more strict, I
> > think.
> The question is now, if USE_LINUX_PREFIX is sufficient. Do we have
> po
Quoting Pav Lucistnik <[EMAIL PROTECTED]> (from Wed, 12 Mar 2008
11:15:53 +0100):
Alexander Leidinger píše v st 12. 03. 2008 v 11:04 +0100:
Quoting Pav Lucistnik <[EMAIL PROTECTED]> (from Tue, 11 Mar 2008
23:45:04 + (UTC)):
> - Teach USE_LDCONFIG to do the right thing when used with
Alexander Leidinger píše v st 12. 03. 2008 v 11:04 +0100:
> Quoting Pav Lucistnik <[EMAIL PROTECTED]> (from Tue, 11 Mar 2008
> 23:45:04 + (UTC)):
>
> > - Teach USE_LDCONFIG to do the right thing when used with USE_LINUX_PREFIX
> >
> > PR: ports/118212
> > http://www.FreeB
Quoting Pav Lucistnik <[EMAIL PROTECTED]> (from Tue, 11 Mar 2008
23:45:04 + (UTC)):
- Teach USE_LDCONFIG to do the right thing when used with USE_LINUX_PREFIX
PR: ports/118212
http://www.FreeBSD.org/cgi/query-pr.cgi?pr=118212
Original patch: vd
Patch by: pav
Quoting Kris Kennaway <[EMAIL PROTECTED]> (Tue, 7 Aug 2007 13:58:56 -0400):
> On Tue, Aug 07, 2007 at 03:37:44PM +0200, Alexander Leidinger wrote:
> > (note: please see my other mail where I inlined scripts to
> > automatically find suitable LIB_DEPENDS lines for the common case)?
>
> I think
Alexander Leidinger schrieb:
> Where should the following (or something similar) be added to?
> ---snip---
> The ports collection now has a knob (EXPLICIT_PACKAGE_DEPENDS) to only
> register the explicit dependencies. It will allow to speed up
> "portupgrade -r" and "portupgrade -R" in the future.
Quoting Michael Nottebrock <[EMAIL PROTECTED]> (from Tue, 07 Aug 2007
19:53:19 +0200):
I think we might possibly be talking past each other - let me rephrase
my concerns about the EXPLICIT_PACKAGE_DEPENDS switch and its functionality:
- I am concerned about users trying to use that switch *no
Quoting Kris Kennaway <[EMAIL PROTECTED]> (Tue, 7 Aug 2007 13:58:56 -0400):
> On Tue, Aug 07, 2007 at 03:37:44PM +0200, Alexander Leidinger wrote:
> > Quoting Kris Kennaway <[EMAIL PROTECTED]> (from Mon, 6 Aug 2007
> > 13:38:08 -0400):
> > >dependencies a better way is to use LIB_ or RUN_DEPEND
Quoting Peter Jeremy <[EMAIL PROTECTED]> (Wed, 8 Aug 2007 04:40:11 +1000):
> On 2007-Aug-07 14:51:23 +0200, Alexander Leidinger <[EMAIL PROTECTED]> wrote:
> >ports. But for some ports you can get the benefit immediately. I hope you
> >are not too biased regarding KDE. Yes, KDE and such would bene
On 2007-Aug-07 14:51:23 +0200, Alexander Leidinger <[EMAIL PROTECTED]> wrote:
>ports. But for some ports you can get the benefit immediately. I hope you
>are not too biased regarding KDE. Yes, KDE and such would benefit by a huge
>amount by this, more than smaller ports, but even for the "small"
On Tue, Aug 07, 2007 at 03:37:44PM +0200, Alexander Leidinger wrote:
> Quoting Kris Kennaway <[EMAIL PROTECTED]> (from Mon, 6 Aug 2007
> 13:38:08 -0400):
>
> >On Mon, Aug 06, 2007 at 01:34:06PM +0200, Michael Nottebrock wrote:
> >>Alexander Leidinger schrieb:
> >>> Kris, what technical reasons a
I think we might possibly be talking past each other - let me rephrase
my concerns about the EXPLICIT_PACKAGE_DEPENDS switch and its functionality:
- I am concerned about users trying to use that switch *now* to cut down
time on portupgrade -r and portupgrade -R operations and getting
inconsistent
Quoting Kris Kennaway <[EMAIL PROTECTED]> (from Mon, 6 Aug 2007
13:38:08 -0400):
On Mon, Aug 06, 2007 at 01:34:06PM +0200, Michael Nottebrock wrote:
Alexander Leidinger schrieb:
> Kris, what technical reasons are against explicit dependencies, in
> your opinion?
Explicit dependencies would be
Quoting Michael Nottebrock <[EMAIL PROTECTED]> (from Tue, 07 Aug 2007
12:42:00 +0200):
Alexander Leidinger schrieb:
Explicit dependencies that need to be determined and maintained manually
by port maintainers are useless, since they'll be almost guaranteed to
be wrong most of the time for t
Alexander Leidinger schrieb:
>
>> Explicit dependencies would be great, if they can be guaranteed to be
>> correct, which basically means we need a way auto-generate them. Maybe
>
> Auto generation would be nice, but it doesn't need to be a hard
> requirement. See below.
>
>> this could be done in
Quoting Michael Nottebrock <[EMAIL PROTECTED]> (from Mon, 06 Aug 2007
13:34:06 +0200):
Alexander Leidinger schrieb:
Kris, what technical reasons are against explicit dependencies, in
your opinion?
Just to make sure we talk about the same: we don't want to disable the
recursive dependency
On Mon, Aug 06, 2007 at 01:34:06PM +0200, Michael Nottebrock wrote:
> Alexander Leidinger schrieb:
> > Kris, what technical reasons are against explicit dependencies, in
> > your opinion?
> Explicit dependencies would be great, if they can be guaranteed to be
> correct, which basically means we ne
Alexander Leidinger schrieb:
> Kris, what technical reasons are against explicit dependencies, in
> your opinion?
Explicit dependencies would be great, if they can be guaranteed to be
correct, which basically means we need a way auto-generate them. Maybe
this could be done in a similar way to the
Alexander Leidinger <[EMAIL PROTECTED]> writes:
> I was tempted to say it also decreases the amount of time for
> incremental package builds, but as the package dependencies change
> (meta data for the portversion or portrevision) all packages which
> have a changed port in their implicit dependenc
Quoting Kris Kennaway <[EMAIL PROTECTED]> (from Mon, 6 Aug 2007
02:56:34 -0400):
On Mon, Aug 06, 2007 at 07:43:18AM +0200, Alexander Leidinger wrote:
>>Not sure this can work reliably enough to be usefule at present, at
>> least for
>>the specific scenario of avoiding unnecessary recompilati
On Mon, Aug 06, 2007 at 07:43:18AM +0200, Alexander Leidinger wrote:
> >>Not sure this can work reliably enough to be usefule at present, at
> >> least for
> >>the specific scenario of avoiding unnecessary recompilations. I think
> >>there
> >>are just too many ports with implicit dependencies,
Quoting Kris Kennaway <[EMAIL PROTECTED]> (from Fri, 3 Aug 2007
16:42:15 -0400):
On Fri, Aug 03, 2007 at 09:44:56PM +0200, Michael Nottebrock wrote:
On Friday, 3. August 2007, Henrik Brix Andersen wrote:
> On Thu, Aug 02, 2007 at 06:17:15PM +0200, Alexander Leidinger wrote:
> > Quoting Henrik
On Friday, 3. August 2007, Henrik Brix Andersen wrote:
> On Thu, Aug 02, 2007 at 06:17:15PM +0200, Alexander Leidinger wrote:
> > Quoting Henrik Brix Andersen <[EMAIL PROTECTED]> (from Thu, 2 Aug
> > 2007
> >
> > 16:17:10 +0200):
> >>> Feature:
> >>> - allow to only register explicit dependencies,
On Fri, Aug 03, 2007 at 09:44:56PM +0200, Michael Nottebrock wrote:
> On Friday, 3. August 2007, Henrik Brix Andersen wrote:
> > On Thu, Aug 02, 2007 at 06:17:15PM +0200, Alexander Leidinger wrote:
> > > Quoting Henrik Brix Andersen <[EMAIL PROTECTED]> (from Thu, 2 Aug
> > > 2007
> > >
> > > 16:17:
On Thu, Aug 02, 2007 at 06:17:15PM +0200, Alexander Leidinger wrote:
> Quoting Henrik Brix Andersen <[EMAIL PROTECTED]> (from Thu, 2 Aug 2007
> 16:17:10 +0200):
>
>>> Feature:
>>> - allow to only register explicit dependencies, disabled by default
>>>(EXPLICIT_PACKAGE_DEPENDS=whatever_you_wa
Quoting Henrik Brix Andersen <[EMAIL PROTECTED]> (from Thu, 2 Aug
2007 16:17:10 +0200):
Feature:
- allow to only register explicit dependencies, disabled by default
(EXPLICIT_PACKAGE_DEPENDS=whatever_you_want)
Can you elaborate a bit on this new EXPLICIT_PACKAGE_DEPENDS feature?
Perhaps
Hi,
On Fri, Jun 29, 2007 at 09:46:35AM +0200, Alexander Leidinger wrote:
> Quoting Pav Lucistnik <[EMAIL PROTECTED]> (from Thu, 28 Jun 2007 15:53:05
> + (UTC)):
>
>> pav 2007-06-28 15:53:05 UTC
>>
>> FreeBSD ports repository
>>
>> Modified files:
>> Mk bsd
Pav Lucistnik wrote:
pav 2007-06-28 16:06:02 UTC
FreeBSD ports repository
Modified files:
Mk bsd.port.mk
Log:
- Add a new virtual category `kld' for ports that install kernel loadable
module
Revision ChangesPath
1.572 +2 -2 ports
Quoting Pav Lucistnik <[EMAIL PROTECTED]> (from Thu, 28 Jun 2007
15:53:05 + (UTC)):
pav 2007-06-28 15:53:05 UTC
FreeBSD ports repository
Modified files:
Mk bsd.port.mk
Log:
- Correct and extend actual-package-depends target, introduced in previous
On May 21, 2007, at 07:35 , Mark Linimon wrote:
On Mon, May 21, 2007 at 03:30:32PM +0200, Dag-Erling Smørgrav wrote:
OK, I didn't realize we were going to remove XFree86 altogether
Unless someone steps up to a) maintain it and b) make a case for its
remaining in the tree and c) regression-te
[EMAIL PROTECTED] (Mark Linimon) writes:
> Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> > OK, I didn't realize we were going to remove XFree86 altogether
> Unless someone steps up to a) maintain it and b) make a case for its
> remaining in the tree and c) regression-test the necessary
> infras
Florent Thoumie <[EMAIL PROTECTED]> writes:
> Also, USE_IMAKE currently implies USE_XLIB, I'm not sure this is really
> needed but I haven't really looked into this yet.
I believe it may have been necessary at some point because the cf files
were installed as part of XFree86-4-libraries. These da
Mark Linimon wrote:
> On Mon, May 21, 2007 at 03:30:32PM +0200, Dag-Erling Smørgrav wrote:
>> OK, I didn't realize we were going to remove XFree86 altogether
>
> Unless someone steps up to a) maintain it and b) make a case for its
> remaining in the tree and c) regression-test the necessary infras
On Mon, May 21, 2007 at 03:30:32PM +0200, Dag-Erling Smørgrav wrote:
> OK, I didn't realize we were going to remove XFree86 altogether
Unless someone steps up to a) maintain it and b) make a case for its
remaining in the tree and c) regression-test the necessary infrastructure.
e.g. "last call" h
Dag-Erling Smørgrav wrote:
> Florent Thoumie <[EMAIL PROTECTED]> writes:
>> Let's just set USE_XLIB=yes if X_WINDOW_SYSTEM == xfree86-4 and USE_XORG
>> is defined.
>
> Yes, that would be the easiest solution.
>
> What about USE_X_PREFIX, BTW? I assume that X.org-aware ports are not
> supposed to
Florent Thoumie <[EMAIL PROTECTED]> writes:
> Let's just set USE_XLIB=yes if X_WINDOW_SYSTEM == xfree86-4 and USE_XORG
> is defined.
Yes, that would be the easiest solution.
What about USE_X_PREFIX, BTW? I assume that X.org-aware ports are not
supposed to define it? Perhaps there should be a ch
Dag-Erling Smørgrav wrote:
> Florent Thoumie <[EMAIL PROTECTED]> writes:
>> Dag-Erling SmÞrgrav <[EMAIL PROTECTED]> wrote:
>>> Florent Thoumie <[EMAIL PROTECTED]> writes:
Log:
Fix USE_XLIB to depend on stub file rather than libX11.
>>> Is this intended as a permanent solution? I rea
Pav Lucistnik <[EMAIL PROTECTED]> writes:
> Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> > Is this intended as a permanent solution? I realize that having
> > USE_XLIB the way it is allows us to support both X.org and XFree86, but
> > I would much prefer to see USE_XLIB replaced with somethin
Florent Thoumie <[EMAIL PROTECTED]> writes:
> Dag-Erling Smørgrav <[EMAIL PROTECTED]> wrote:
> > Florent Thoumie <[EMAIL PROTECTED]> writes:
> > > Log:
> > > Fix USE_XLIB to depend on stub file rather than libX11.
> > Is this intended as a permanent solution? I realize that having
> > USE_XLIB
Dag-Erling Smørgrav wrote:
> Florent Thoumie <[EMAIL PROTECTED]> writes:
>
>> flz 2007-05-21 10:21:39 UTC
>>
>> FreeBSD ports repository
>>
>> Modified files:
>> Mk bsd.port.mk
>> Log:
>> Fix USE_XLIB to depend on stub file rather than libX11.
>
> Is this in
Dag-Erling Smørgrav píše v po 21. 05. 2007 v 13:38 +0200:
> Florent Thoumie <[EMAIL PROTECTED]> writes:
>
> > flz 2007-05-21 10:21:39 UTC
> >
> > FreeBSD ports repository
> >
> > Modified files:
> > Mk bsd.port.mk
> > Log:
> > Fix USE_XLIB to depend on stub f
Florent Thoumie <[EMAIL PROTECTED]> writes:
> flz 2007-05-21 10:21:39 UTC
>
> FreeBSD ports repository
>
> Modified files:
> Mk bsd.port.mk
> Log:
> Fix USE_XLIB to depend on stub file rather than libX11.
Is this intended as a permanent solution? I realize
On Sat, Apr 07, 2007 at 12:51:48PM +, Pav Lucistnik wrote:
> pav 2007-04-07 12:51:48 UTC
>
> FreeBSD ports repository
>
> Modified files:
> Mk bsd.port.mk
> Log:
> - Fix regression in makesum target introduced with rev. 1.561
Thank you!
Regards,
Rong-E
in message <[EMAIL PROTECTED]>,
wrote Pav Lucistnik thusly...
...
> Modified files:
> Mk bsd.port.mk
> Log:
> - Add a code to invalidate saved OPTIONS when the set of OPTIONS
> defined in a port changes.
Nice, thanks.
> The end user inpact of this is more blue scre
On 1/8/07, Pav Lucistnik <[EMAIL PROTECTED]> wrote:
pav 2007-01-08 00:00:33 UTC
FreeBSD ports repository
Modified files:
Mk bsd.port.mk bsd.tcl.mk
Log:
- Fix USE_TCL_BUILD to not disable runtime dependency on tcl from USE_TCL
- Add a new knob: USE_TK_BUIL
Joe Marcus Clarke wrote:
> Sergey Matveychuk wrote:
>>> Joe Marcus Clarke wrote:
On Thu, 2006-06-29 at 11:34 +0400, Sergey Matveychuk wrote:
> Joe Marcus Clarke wrote:
>> This, of course, would not cause the error. As I said to Mark in a
>> follow-up email, it may very well be tim
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sergey Matveychuk wrote:
> Joe Marcus Clarke wrote:
>> On Thu, 2006-06-29 at 11:34 +0400, Sergey Matveychuk wrote:
>>> Joe Marcus Clarke wrote:
This, of course, would not cause the error. As I said to Mark in a
follow-up email, it may very w
Joe Marcus Clarke wrote:
> On Thu, 2006-06-29 at 11:34 +0400, Sergey Matveychuk wrote:
>> Joe Marcus Clarke wrote:
>>> This, of course, would not cause the error. As I said to Mark in a
>>> follow-up email, it may very well be time to retire DEPENDS, but the
>>> patch that was committed did not su
On Thu, 2006-06-29 at 11:34 +0400, Sergey Matveychuk wrote:
> Joe Marcus Clarke wrote:
> >
> > This, of course, would not cause the error. As I said to Mark in a
> > follow-up email, it may very well be time to retire DEPENDS, but the
> > patch that was committed did not successfully do that and
Joe Marcus Clarke wrote:
>
> This, of course, would not cause the error. As I said to Mark in a
> follow-up email, it may very well be time to retire DEPENDS, but the
> patch that was committed did not successfully do that and maintain the
> buildability of the tree.
>
Using FORCE_PKG_REGISTER
On Tue, 2006-06-27 at 17:38 -0500, Mark Linimon wrote:
> On Wed, Jun 28, 2006 at 02:11:01AM +0400, Sergey Matveychuk wrote:
> > Can I see a log for this breakage?
>
> Unfortunately I went ahead and cleared the i386-6-exp logfiles out about
> an hour ago to get ready for the next build. On top of
On Wed, Jun 28, 2006 at 02:11:01AM +0400, Sergey Matveychuk wrote:
> Can I see a log for this breakage?
Unfortunately I went ahead and cleared the i386-6-exp logfiles out about
an hour ago to get ready for the next build. On top of that, I had already
rerun kdelibs3* on both i386-6 and i386-5-exp
Mark Linimon wrote:
> linimon 2006-06-26 23:39:09 UTC
>
> FreeBSD ports repository
>
> Modified files:
> Mk bsd.port.mk
> Log:
> Revert ports/95841. It breaks kdelibs3. I didn't spot this because
> kdelibs3
> had failed to build before this patch, but for o
On Thu, 20 Apr 2006 11:36:31 +0300
Alexandr Kovalenko <[EMAIL PROTECTED]> wrote:
> Hello, Kris Kennaway!
>
> On Thu, Feb 23, 2006 at 08:28:14AM +, you wrote:
>
> > kris2006-02-23 08:28:14 UTC
> >
> > FreeBSD ports repository
> >
> > Modified files:
> > Mk
Hello, Kris Kennaway!
On Thu, Feb 23, 2006 at 08:28:14AM +, you wrote:
> kris2006-02-23 08:28:14 UTC
>
> FreeBSD ports repository
>
> Modified files:
> Mk bsd.port.mk
> Log:
> * Back out the PERL_(BUILD|RUN)_DEPENDS. It needs to be reimplemented
>
78 matches
Mail list logo
