> On Oct 7, 2016, at 8:09 AM, Ryan Schmidt wrote:
>
>
>> On Oct 7, 2016, at 9:48 AM, Bradley Giesbrecht wrote:
>>
>> Hi,
>>
>>
>> mariadb-server is a support of mariadb.
>>
>>
>> In post-extract I copy a file from filespath
> On Oct 7, 2016, at 9:48 AM, Bradley Giesbrecht wrote:
>
> Hi,
>
>
> mariadb-server is a support of mariadb.
>
>
> In post-extract I copy a file from filespath and in post-patch I patch the
> file with reinplace:
> port cat mariadb-server:
> ...
>
Hi,
mariadb-server is a support of mariadb.
In post-extract I copy a file from filespath and in post-patch I patch the file
with reinplace:
port cat mariadb-server:
...
post-extract {
file mkdir ${worksrcpath}/macports
copy ${filespath}/org.macports.mysql-server.plist
Hi,
- On 4 Oct, 2014, at 16:25, Joshua Root j...@macports.org wrote:
>> I’m writing an updating port for the new version of gis/gdal.
>>
>> However, the port does not compile because a .h file installed by the old
>> version into ${prefix}/include masks a new version of the same .h bundled
tract {
> file copy ${worksrcpath}/port/cpl_port.h ${worksrcpath}/port/Cpl_port.h
> set files_to_patch [exec find ${worksrcpath} -type f -exec grep -l
> "cpl_port.h" \{\} \;]
> foreach file ${files_to_patch} {
> # DEBUG
> puts ${file}
>
ort.h" \{\} \;]
foreach file ${files_to_patch} {
# DEBUG
puts ${file}
reinplace "s|cpl_port.h|Cpl_port.h|" ${file}
}
}
However, the procedure fails at a certain point for an unknown reason:
/opt/…/frmts/grib/degrib18/degrib/grib2api.c
/opt/…/frmts/grib/degrib18/
On Sep 27, 2014, at 11:06 AM, Brandon Allbery wrote:
> On Sat, Sep 27, 2014 at 11:59 AM, Kurt Hindenburg wrote:
>> Hi, I find reinplace easier and less work for new releases. Are there
>> reasons to use one over the other?
>
> reinplace is appropriate for replacing self-c
On Sat, Sep 27, 2014 at 11:59 AM, Kurt Hindenburg wrote:
> Hi, I find reinplace easier and less work for new releases. Are there
> reasons to use one over the other?
reinplace is appropriate for replacing self-contained "tokens" and such.
When the context of an edit is impo
Hi, I find reinplace easier and less work for new releases. Are there
reasons to use one over the other?
Kurt
Revision: 125845
https://trac.macports.org/changeset/125845
Author:ryandesign at macports.org
<https://lists.macosforge.org/mailman/listinfo/macports-changes>
On Jul 13, 2014, at 4:07 PM, Mark Brethen wrote:
> On Jul 13, 2014, at 3:28 PM, Jeremy Lavergne wrote:
>
>> On Jul 13, 2014, at 16:18, Mark Brethen wrote:
>>
>>> In need to reinplace the CMakeLists file in each subdirectory, replacing
>>> '
On Jul 13, 2014, at 3:28 PM, Jeremy Lavergne wrote:
> I’d use fs-traverse, filtering to just the specific files you’re after.
>
> On Jul 13, 2014, at 16:18, Mark Brethen wrote:
>
>> In need to reinplace the CMakeLists file in each subdirectory, replacing
>> '
I’d use fs-traverse, filtering to just the specific files you’re after.
On Jul 13, 2014, at 16:18, Mark Brethen wrote:
> In need to reinplace the CMakeLists file in each subdirectory, replacing
> 'Mod/(subdirectory)' with 'lib/${name}/Mod/(subdirectory). How do you w
On Jul 13, 2014, at 3:18 PM, Mark Brethen wrote:
> Given a directory tree
>
> src/Mod
> |-- Arch
> |-- Assembly
> |-- Cam
> |-- CMakeFiles
> |-- Complete
>
> In need to reinplace the CMakeLists file in each subdirectory, replacing
&g
Given a directory tree
src/Mod
|-- Arch
|-- Assembly
|-- Cam
|-- CMakeFiles
|-- Complete
In need to reinplace the CMakeLists file in each subdirectory, replacing
'Mod/(subdirectory)' with 'lib/${name}/Mod/(subdirectory). How do you write a
tcl loo
That explains why pipe didn't work as well.
Thanks.
Sent from my iPhone
> On Jul 7, 2014, at 1:59 PM, Brandon Allbery wrote:
>
>> On Mon, Jul 7, 2014 at 2:30 PM, Mark Brethen wrote:
>> I only need to replace the uncommented line. So I tried
>>
>>
On Mon, Jul 7, 2014 at 2:30 PM, Mark Brethen wrote:
> I only need to replace the uncommented line. So I tried
>
> post-configure {
> reinplace {:^#:!s:Inventor/scxml:scxml:g} \
> ${worksrcpath}/src/3rdParty/CMakeLists.txt
> }
>
> But this had no effect, when i
tried
post-configure {
reinplace {:^#:!s:Inventor/scxml:scxml:g} \
${worksrcpath}/src/3rdParty/CMakeLists.txt
}
But this had no effect, when it should work in sed. Am I missing something?
Mark
___
macports-dev mailing list
macports-dev
> Don’t do this reinplacement on binary files.
>
> https://trac.macports.org/ticket/35581
>
Sure, that was my intent when noticing it, but I was still wondering about the
best way of doing it, as filtering by file extension could have been cumbersome
and possibly not reliable.
I was however no
On Jan 5, 2014, at 03:23, Nicolas Pavillon wrote:
> However, this way also applies reinplace to binary files, and adds a “0A”
> line feed at the end of the file. One obvious way would be to filter through
> file extensions, but this may become quite cumbersome. Would anyone have a
On Jan6, 2014, at 1:03, Joshua Root wrote:
> The reinplace proc is just a front-end to sed(1), which is a
> line-oriented tool and thus the wrong choice for modifying binaries. So
> yes, I'd say you need to not run it on the binaries, one way or another.
All right, thank
On 2014-1-5 20:23 , Nicolas Pavillon wrote:
> Hello,
>
> I noticed that the “reinplace” instruction is automatically adding a line
> feed to files, which is causing problems with some binary files which should
> have a predefined length.
>
> In particular, there is a s
files that contain that header.
>fs-traverse item ${worksrcpath} {
>if {[file isfile ${item}]} {
>reinplace -locale C "/#include/s@Phonon@phonon@" ${item}
>}
>}
> }
>
> However, this way also applies reinplace to binary files, and
Hello,
I noticed that the “reinplace” instruction is automatically adding a line feed
to files, which is causing problems with some binary files which should have a
predefined length.
In particular, there is a set of instructions in the kde4-1.1 portgroup which
scans all files to replace an
wrote:
> Hi:
>
> I've noticed a number of commits recently inserting "-locale C" into
> reinplace commands (example below). Google didn't point to an explanation so
> I wonder if someone could give me a brief description?
>
> Thanks,
>
> Craig
Hi:
I've noticed a number of commits recently inserting "-locale C" into
reinplace commands (example below). Google didn't point to an
explanation so I wonder if someone could give me a brief description?
Thanks,
Craig
From: ryandes...@macports.o
At 1:10 AM -0500 4/3/12, Ryan Schmidt wrote:
On Apr 2, 2012, at 19:55, Craig Treleaven wrote:
At 4:27 PM -0500 4/2/12, Ryan Schmidt wrote:
On Apr 2, 2012, at 14:35, Joshua Root wrote:
Does just "find ${configure.dir} -name Makefile" also give unexpected
results?
The "find" correctly f
On Apr 2, 2012, at 19:55, Craig Treleaven wrote:
> At 4:27 PM -0500 4/2/12, Ryan Schmidt wrote:
>> On Apr 2, 2012, at 14:35, Joshua Root wrote:
>>
>>> Does just "find ${configure.dir} -name Makefile" also give unexpected
>>> results?
>>
>> The "find" correctly finds 28 files named "Makefile". I
At 6:31 PM -0700 4/2/12, Bradley Giesbrecht wrote:
Content-type: multipart/signed; boundary=Apple-Mail-15-774700747;
protocol="application/pkcs7-signature"; micalg=sha1
On Apr 2, 2012, at 6:04 PM, Craig Treleaven wrote:
At 8:55 PM -0400 4/2/12, Craig Treleaven wrote:
At 4:27 PM -0500 4/2/
On Apr 2, 2012, at 6:04 PM, Craig Treleaven wrote:
> At 8:55 PM -0400 4/2/12, Craig Treleaven wrote:
>> At 4:27 PM -0500 4/2/12, Ryan Schmidt wrote:
>>> On Apr 2, 2012, at 14:35, Joshua Root wrote:
>>>
Does just "find ${configure.dir} -name Makefile" also give unexpected
results?
>>>
At 8:55 PM -0400 4/2/12, Craig Treleaven wrote:
At 4:27 PM -0500 4/2/12, Ryan Schmidt wrote:
On Apr 2, 2012, at 14:35, Joshua Root wrote:
Does just "find ${configure.dir} -name Makefile" also give unexpected
results?
The "find" correctly finds 28 files named "Makefile". It correctly
remov
At 4:27 PM -0500 4/2/12, Ryan Schmidt wrote:
On Apr 2, 2012, at 14:35, Joshua Root wrote:
Does just "find ${configure.dir} -name Makefile" also give unexpected
results?
The "find" correctly finds 28 files named "Makefile". It correctly
removes " -L " from 22 of them. The remaining 6 are in
On Apr 2, 2012, at 14:35, Joshua Root wrote:
> Does just "find ${configure.dir} -name Makefile" also give unexpected
> results?
The "find" correctly finds 28 files named "Makefile". It correctly removes " -L
" from 22 of them. The remaining 6 are in the directory
mythplugins/mythweather/mythwe
At 3:14 PM -0500 4/2/12, Ryan Schmidt wrote:
On Apr 2, 2012, at 14:13, Craig Treleaven wrote:
Ryan, for building, remember that you need qt-4mac +mysql +debug.
You said I needed +mysql before so I rebuilt with that. Why do I
need +debug as well? I don't want my computer slow for another
en
On Apr 2, 2012, at 14:13, Craig Treleaven wrote:
> Ryan, for building, remember that you need qt-4mac +mysql +debug.
You said I needed +mysql before so I rebuilt with that. Why do I need +debug as
well? I don't want my computer slow for another entire day while I rebuild
qt4-mac yet again.
_
t;
> That still doesn't explain, though, why find proceeds merrily for 22 of
> the 78 directories and then quits without error.
Jeremy and I were talking about your reinplace line. Yes, the system
command runs a shell, and I don't see anything wrong with the way you're
using
Think so: It's being parsed by tcl and then passed through
Craig Treleaven wrote:
>At 5:14 AM +1000 4/3/12, Joshua Root wrote:
>>On 2012-4-3 04:01 , Jeremy Lavergne wrote:
Nope, none of those characters have special meanings to Tcl nor
to the regular expression engine. It looks like a
At 3:25 PM -0400 4/2/12, Craig Treleaven wrote:
At 5:14 AM +1000 4/3/12, Joshua Root wrote:
On 2012-4-3 04:01 , Jeremy Lavergne wrote:
Nope, none of those characters have special meanings to Tcl nor
to the regular expression engine. It looks like a perfectly valid
regular expression to me. Ho
At 5:14 AM +1000 4/3/12, Joshua Root wrote:
On 2012-4-3 04:01 , Jeremy Lavergne wrote:
Nope, none of those characters have special meanings to Tcl nor
to the regular expression engine. It looks like a perfectly valid
regular expression to me. Hopefully it will become clearer to me
when I actu
On 2012-4-3 04:01 , Jeremy Lavergne wrote:
>> Nope, none of those characters have special meanings to Tcl nor to the
>> regular expression engine. It looks like a perfectly valid regular
>> expression to me. Hopefully it will become clearer to me when I actually try
>> to build the port. Please
At 12:56 PM -0500 4/2/12, Ryan Schmidt wrote:
On Apr 2, 2012, at 12:39, Craig Treleaven wrote:
Maybe that's the problem--it is not supposed to be a "regular
expression"; it is a literal string of 'space-hyphen-capital
ell-space'. Does hyphen have special meaning in a regex?
Nope, none of t
> Nope, none of those characters have special meanings to Tcl nor to the
> regular expression engine. It looks like a perfectly valid regular expression
> to me. Hopefully it will become clearer to me when I actually try to build
> the port. Please hold on. My computer is currently occupied upgr
On Apr 2, 2012, at 12:39, Craig Treleaven wrote:
> Maybe that's the problem--it is not supposed to be a "regular expression"; it
> is a literal string of 'space-hyphen-capital ell-space'. Does hyphen have
> special meaning in a regex?
Nope, none of those characters have special meanings to Tc
;
sudo find . -name "Makefile" -exec sed -i '' 's/ -L / /g' {} \;
This is what MacPorts Reinplace extension is for, right? Would
this be the right syntax?
post-configure {
reinplace 's/ -L / /g' ${worksrcpath}/Makefile
}
Reinplace will do a r
-name "Makefile" -exec sed -i '' 's/ -L / /g' {} \;
>>>
>>> This is what MacPorts Reinplace extension is for, right? Would this be the
>>> right syntax?
>>>
>>> post-configure {
>>> reinplace 's/ -L /
At 10:20 AM -0400 3/31/12, Jeremy Lavergne wrote:
> cd cd
"/opt/local/var/macports/build/_Users_craigtreleaven_MacPortsTemp_Myth.25/mythtv/work/mythtv-v0.25-rc-0-g92f7d1f/mythtv"
sudo find . -name "Makefile" -exec sed -i '' 's/ -L / /g' {} \;
This
> cd cd
> "/opt/local/var/macports/build/_Users_craigtreleaven_MacPortsTemp_Myth.25/mythtv/work/mythtv-v0.25-rc-0-g92f7d1f/mythtv"
> sudo find . -name "Makefile" -exec sed -i '' 's/ -L / /g' {} \;
>
> This is what MacPorts Reinplace exte
_Myth.25/mythtv/work/mythtv-v0.25-rc-0-g92f7d1f/mythtv"
sudo find . -name "Makefile" -exec sed -i '' 's/ -L / /g' {} \;
This is what MacPorts Reinplace extension is for, right? Would this
be the right syntax?
post-configure {
reinplace 's/ -L /
Any objections to adding sed's -n switch to reinplace? Having this available
would let us solve a problem with perl ports. The proposal and patch are here:
http://trac.macports.org/ticket/26406
___
macports-dev mailing list
macport
On 2009-05-30 00:11, Darren Weber wrote:
> An example of how to remove a line with some search text in it. Assume
> tmp.txt contains:
>
> # BEGIN (not in file)
> abc
> def
> # END (not in file)
>
> reinplace {$!N;s|^.*abc.*\\n||g} tmp.txt
Easier sed syntax to remove
An example of how to remove a line with some search text in it. Assume
tmp.txt contains:
# BEGIN (not in file)
abc
def
# END (not in file)
reinplace {$!N;s|^.*abc.*\\n||g} tmp.txt
If you need to include variables -- escape, escape, escape!
set abcVar abc
reinplace "\$!N;s|^.*${abcVar}.*\
>> > Following the wiki dev tips, I'm doing this:
>> >
>> > rlwrap tclsh8.4
>> > % source /Library/Tcl/macports1.0/macports_fastload.tcl
>> > % package require Pextlib
>> >
>> > It doesn't provide the 'reinplace' c
On May 27, 2009, at 3:28 PM, Darren Weber wrote:
PS, I know grep isn't glob ;-) The grep was a bash command to
search all the macport .tcl files.
Indeed, but "*reinplace*" means it's looking for the literal string
"*reinplac" followed by 0 or
quire Pextlib
> >
> > It doesn't provide the 'reinplace' command. Also, the following comes
> > up with nothing:
> >
> > grep "*reinplace*" /Library/Tcl/macports1.0/*
> >
> > Where is this little gem and can it be required in tclsh
On 2009-05-27 23:23, Darren Weber wrote:
>
> Following the wiki dev tips, I'm doing this:
>
> rlwrap tclsh8.4
> % source /Library/Tcl/macports1.0/macports_fastload.tcl
> % package require Pextlib
>
> It doesn't provide the 'reinplace' command.
On May 27, 2009, at 2:23 PM, Darren Weber wrote:
Following the wiki dev tips, I'm doing this:
rlwrap tclsh8.4
% source /Library/Tcl/macports1.0/macports_fastload.tcl
% package require Pextlib
It doesn't provide the 'reinplace' command. Also, the following
comes up
Following the wiki dev tips, I'm doing this:
rlwrap tclsh8.4
% source /Library/Tcl/macports1.0/macports_fastload.tcl
% package require Pextlib
It doesn't provide the 'reinplace' command. Also, the following comes up
with nothing:
grep "*reinplace*" /Library/Tc
backslash escapes from the tcl interpreter. The
next backslash espaces from the regular expression engine.
reinplace "s|\\.\\./lib/${name}|\\.\\./lib/${distname}|g"} ${destroot}
${findITKbranch}
If you don't need any variables in your regular expression, you can
enclose it
It likely needs a double escape.
Try \\.
Good luck!
On May 27, 2009, at 2:47 AM, Darren Weber wrote:
That doesn't work. I don't understand how this is parsed through
the tcl and port parsers. How would you do it?
smime.p7s
Description: S/MIME cryptographic signature
oolkit-3.12"
However, when the \. is used in reinplace for a Portfile, e.g.:
reinplace "s|\.\./lib/${name}|\.\./lib/${distname}|g"}
${destroot}${findITKbranch}
The result is the same as the second example above (i.e. PREFIX becomes
PREF..).
I also tried this:
reinplace {"s|[.][.]/
On Mar 20, 2009, at 6:25 PM, Rainer Müller wrote:
Bradley Giesbrecht wrote:
This is what I ended up with to escape double quotes. I'm sure
someone
here will show me a better way.
set CCARGS [concat ${CCARGS} -DUSE_SASL_AUTH -
DDEF_SERVER_SASL_TYPE=\\"dovecot\\"]
First, the
Bradley Giesbrecht wrote:
> This is what I ended up with to escape double quotes. I'm sure someone
> here will show me a better way.
>
> set CCARGS [concat ${CCARGS} -DUSE_SASL_AUTH -
> DDEF_SERVER_SASL_TYPE=\\"dovecot\\"]
First, there is usually no need to do:
set foo [conc
Rainer Müller wrote:
> Rainer Müller wrote:
>
>> You have to quote the replace pattern, otherwise &|g is interpreted as a
>> filename.
>>
>> reinplace "s|psppire|psppire &|g" ...
>
> And please note that & does not do here what it
Rainer Müller wrote:
> You have to quote the replace pattern, otherwise &|g is interpreted as a
> filename.
>
> reinplace "s|psppire|psppire &|g" ...
And please note that & does not do here what it usually does with sed.
It will not be replaced with the m
On Mar 20, 2009, at 7:21 AM, Jeremy Lavergne wrote:
If I want to append a space and ampersand at the end of a known
line, what's the way to write this in reinplace?
I tried (without success):
reinplace s|psppire|psppire &|g
reinplace s|psppire|psppire\ &|g
reinplace s|ps
Jeremy Lavergne wrote:
> If I want to append a space and ampersand at the end of a known line,
> what's the way to write this in reinplace?
>
> I tried (without success):
> reinplace s|psppire|psppire &|g
> reinplace s|psppire|psppire\ &|g
>
If I want to append a space and ampersand at the end of a known line,
what's the way to write this in reinplace?
I tried (without success):
reinplace s|psppire|psppire &|g
reinplace s|psppire|psppire\ &|g
reinplace s|psppire|psppire\ \&|g
Any suggestions?
smim
On Jun 5, 2008, at 00:04, Jordan Hubbard wrote:
> On Jun 4, 2008, at 9:37 PM, Joshua Root wrote:
>
>> Ryan Schmidt wrote:
>>
>>> Can I get an opinion from our port authors? I think MacPorts should
>>> at least issue a warning (if not error out entirely) when a
Ryan Schmidt wrote:
> Can I get an opinion from our port authors? I think MacPorts should
> at least issue a warning (if not error out entirely) when a reinplace
> command doesn't end up changing a file. Do you agree?
>
> I filed a ticket with a patch:
>
> http:
Can I get an opinion from our port authors? I think MacPorts should
at least issue a warning (if not error out entirely) when a reinplace
command doesn't end up changing a file. Do you agree?
I filed a ticket with a patch:
http://trac.macports.org/ticket/
Le 07-04-01 à 10:05, Elias Pipping a écrit :
On Apr 1, 2007, at 3:39 PM, Yves de Champlain wrote:
On the other hand, maybe some grepper could translate that in
'basic mode' for me ?
sed -E 's|\$\(DESTDIR\)[[:space:]]+\$\(|\$\(DESTDIR\)\$\(|g'
sed 's|\$(DESTDIR)[[:space:]][[:space:]]*\$(|
On Apr 1, 2007, at 3:39 PM, Yves de Champlain wrote:
On the other hand, maybe some grepper could translate that in
'basic mode' for me ?
sed -E 's|\$\(DESTDIR\)[[:space:]]+\$\(|\$\(DESTDIR\)\$\(|g'
sed 's|\$(DESTDIR)[[:space:]][[:space:]]*\$(|FOO|g'
changes
$(DESTDIR) $(
to
FOO
if
Le 07-04-01 à 03:02, Cédric Luthi a écrit :
On 1 avr. 07, at 08:03, Ryan Schmidt wrote:
Wouldn't most of the existing invocations of reinplace break if we
change that now?
I'd say no. Replacing sed -E by sed would break all those who
actually use extended syntax but probab
On 1 avr. 07, at 08:03, Ryan Schmidt wrote:
Wouldn't most of the existing invocations of reinplace break if we
change that now?
I'd say no. Replacing sed -E by sed would break all those who
actually use extended syntax but probably not the other way round. I
don't thin
On Mar 31, 2007, at 22:53, Yves de Champlain wrote:
Any reason reinplace does not call sed with -E (extended grep
patterns) ?
Wouldn't most of the existing invocations of reinplace break if we
change that now?
___
macports-dev mailing
Hi
Any reason reinplace does not call sed with -E (extended grep
patterns) ?
yves
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-dev
75 matches
Mail list logo
