t; for new portnames. Is my understanding incorrect?
I believe the rule is actually that portnames should not *start* with
an upper-case letter, but that it is allowed in the rest of the name.
That is what the Porter's Handbook says anyway.
--
Erik Trulsson
ertr1...@student.uu.se
On Thu, Dec 17, 2009 at 01:10:02AM -0600, Mark Linimon wrote:
> On Thu, Dec 17, 2009 at 07:25:47AM +0100, Erik Trulsson wrote:
> > I disagree about it being deprecated. The port is only partially superceded
> > by the online website. Since the port includes both server and client
s
that you control in addition to connecting to any 'official' servers. The
online website is not as flexible (and it requires a flash-enabled
webbrowser too which as we all know is not so easily obtained on FreeBSD.)
--
Erik Trulsson
ertr1...@student.uu.se
st
> archivers/zlib/files patch-configure
> Log:
> A Massively Spiffy Yet Delicately Unobtrusive Compression Library
Unless I have missed something, this library is already in the base FreeBSD
system and has been there for several years. What is the point in having it
in the
done about them at the moment.
The policy so far has been that nothing should be done about badly named
files already in the ports tree - renaming them is not worth the pain and
repository churn that would result.
One should however avoid adding *new* file
this list which
went into more detail.
(The thread started with the message found at:
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=889438+0+archive/2008/cvs-all/20080706.cvs-all
)
--
Erik Trulsson
[EMAIL PROTECTED]
___
cvs-all@freebsd.org mailing
The rest of the
name may contain capital letters, so use your own discretion when you are
converting a software name that has some capital letters in it.) There is
a tradition of naming Perl 5 modules by prepending p5- and converting the
double-colon separator to a hyphen; for example, the Data
>
> While it's "nice-to-have" feature, I see no pressing need to MFC this
> interface.
Nor is there any pressing need not to MFC it.
--
Erik Trulsson
[EMAIL PROTECTED]
___
cvs-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
to my knowledge.
Those are all good reasons for why using 'int64_t' would be OK.
None of it is a reason for why using 'long long' would not be OK when you
want at least 64 bits, but do not require exactly 64 bits.
--
Erik Trulsson
[EMAIL PROTECTED]
___
cvs-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
pectation has been broken in the past, but I
suspect it is not all that often.
> AFAIK, we have _never_ promised anything wrt forward compat, only backwards
> ABI compat. I can agree with Robert above that during a transition time such
> as now it's really handy to be able to swi
t test the DEVICE_POLLING case.
In Jack's defense that particular problem was apparently beacuse a 7.x
interface was left in the code (bus_setup_intr(9) takes one more argument
in 7.x than it does in 6.x.) That would not have been caught by having
the code go into -CURRENT first.
--
Erik Trulsson
[EMAI
On Fri, Oct 05, 2007 at 05:05:05PM -0700, Jack Vogel wrote:
> On 10/5/07, Erik Trulsson <[EMAIL PROTECTED]> wrote:
> > On Fri, Oct 05, 2007 at 10:49:09PM +, Jack F Vogel wrote:
> > > jfv 2007-10-05 22:49:09 UTC
> > >
> > > FreeBSD s
e
in -CURRENT (which seems to be version 6.5.3) ? If this is indeed the
case, then shouldn't this code have gone into -CURRENT first?
--
Erik Trulsson
[EMAIL PROTECTED]
___
cvs-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
gt; Actually, I'm not sure standard practice here. Should it be kept in
> both NOTES and GENERIC? Maybe I should not have removed it from NOTES.
>
NOTES should contain just about every single kernel config option there is.
It is intended as a reference as to what you can put into a
before which I would call a POLA-violation (I
was a bit surprised anyway.)
It also seems to introduce a circular dependency.
An MFC of rev. 1.143 of etc/rc.d/netoptions seems to fix these problems.
--
Erik Trulsson
[EMAIL PROTECTED]
___
cvs-all@freebsd.or
t's documented in the bsd.port.mk comments.
>
No, it is actually not documented there.
Since 20060108 it is mentioned in the Porter's Handbook (partly in response
to the above question, I believe), but before that it was not actually
documented *anywhere* that I could find.
-
(via PAE) in an x86 CPU was
first introduced with the Pentium Pro in November 1995, almost exactly a
decade ago.
--
Erik Trulsson
[EMAIL PROTECTED]
___
cvs-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
17 matches
Mail list logo
