Kevin Ballard <[EMAIL PROTECTED]> on Thursday, January 25, 2007 at 7:10
PM -0800 wrote:
>If you create a new Portfile, you should set svn:eol-style to native on
>it (`svn propset svn:eol-style native Portfile`).
>
>
>If you add any patches to the repository, don't set any properties on
>them.
>
>
>
Le 26 janv. 07 à 01:42, Kevin Ballard a écrit :
On Jan 24, 2007, at 6:48 PM, Paul Guyot wrote:
Le 24 janv. 07 à 07:12, Kevin Ballard a écrit :
Hrm, nobody has responded. I guess nobody cares?
If I don't hear anything back in the next few days, I'll go ahead
and commit the change.
I wro
Suggest I Twiki entry about this in big letters right near how add a new
port.
-- Sal
smile.
--
Salvatore Domenick Desiano
Doctoral Candidate
Robotics Institute
Carnegie Mellon University
On Thu, 25 Jan 2007, Kevin Ballard wrote:
o Ok, turns out I wasn't payin
Ok, turns out I wasn't paying enough attention. The "handful" of
binary files were actually all the binary files, whether or not they
had svn:eol-style set. It turns out that the 2 image files I looked
at were the only files that actually had it set ;)
In any case, avoid doing this in the f
On Jan 25, 2007, at 10:04 PM, Mark Duling wrote:
Kevin Ballard <[EMAIL PROTECTED]> on Thursday, January 25, 2007
at 6:54
PM -0800 wrote:
In the future, please try and use the right properties. svn:eol-style
native belongs on files which are line-ending-agnostic, like text
files,
shell scrip
Kevin Ballard <[EMAIL PROTECTED]> on Thursday, January 25, 2007 at 6:54
PM -0800 wrote:
>In the future, please try and use the right properties. svn:eol-style
>native belongs on files which are line-ending-agnostic, like text files,
>shell scripts, tcl scripts, and other source files. Patchfiles mu
At this very moment I am committing a bunch of changes to properties.
Unfortunately it's going to come across as... wow, 39 commits
(assuming there are changes in every category, which there probably
are). That's because I'm committing once per category because of
issues I had trying to com
I'm personally fond of just patch-. The .diff seems
redundant, what with the patch- already there.
On Jan 25, 2007, at 2:26 PM, Ryan Schmidt wrote:
On Jan 25, 2007, at 02:26, Randall Wood wrote:
I have seen no standard that states how patch files are to be named
I have:
http://darwinport
On Jan 24, 2007, at 11:35, Blair Zajac wrote:
Why not just remove the eol-style on files that have a broken build?
Note that this by itself would not be effective. Setting svn:eol-
style to any value causes Subversion to convert the file to LF line
endings internally when storing it in the
On Jan 24, 2007, at 16:22, Kevin Ballard wrote:
I did a pass through Portfiles a while ago to set it on every
Portfile.
And any Portfiles which have been added since then probably never
got it set.
At the time, we discussed that a pre-commit hook should be added to
the repository which
On Jan 25, 2007, at 02:26, Randall Wood wrote:
I have seen no standard that states how patch files are to be named
I have:
http://darwinports.opendarwin.org/docs/ch04s07.html
"The standard convention is to name the patch file 'patch-
.diff, with one diff file per file altered in the source.
Fair enough. I'll stick with native.
On Jan 25, 2007, at 12:48 PM, Blair Zajac wrote:
The point for svn:eol-style native is to allow people to check out
files and edit them on their own box and not have to worry about
the end of lines.
If we set the style to LF, then people that do check t
Kevin Ballard wrote:
On Jan 25, 2007, at 3:26 AM, Randall Wood wrote:
I disagree. Take it off of the */*/patch* and the 200 other patches,
which I guess are poorly named then since they don't start with the
word patch, and leave everything else alone.
I have seen no standard that states h
On Jan 24, 2007, at 6:48 PM, Paul Guyot wrote:
Le 24 janv. 07 à 07:12, Kevin Ballard a écrit :
Hrm, nobody has responded. I guess nobody cares?
If I don't hear anything back in the next few days, I'll go ahead
and commit the change.
I wrote those lines because we use readdir native comman
On Jan 25, 2007, at 3:26 AM, Randall Wood wrote:
I disagree. Take it off of the */*/patch* and the 200 other
patches, which I guess are poorly named then since they don't
start with the word patch, and leave everything else alone.
I have seen no standard that states how patch files are to
On 23/01/07 18:19, Mark Duling wrote:
> phase. I think it is ugly but I don't know of a better way. Does anyone
> else? I attached your patch to to
> http://trac.macports.org/projects/macports/ticket/10679. I want to see if
> anyone has a better idea and if you want to try to deal with the .tur
On 24 Jan 2007, at 16:06, Blair Zajac wrote:
Kevin Ballard wrote:
I'm not seeing a problem right now, because all of the current
patchfiles are supposed to have unix line endings.
But some time ago there was a problem - a patchfile I submitted
had mixed line endings, and the committer conve
Garrett Reid <[EMAIL PROTECTED]> on Wednesday, January 24, 2007
at 8:00 PM -0800 wrote:
For some reason, I'm having issues installing ettercap. It's been
installed before with a previous darwinports install (but I had to
remove it, because wireshark wasn't building). Now, with the newest
darwinp
18 matches
Mail list logo
