Also the last line is misspelled, I think you mean "place where you have write access".
On Wed, Oct 19, 2016 at 7:35 PM, Ryan Schmidt <ryandes...@macports.org> wrote: > > > On Oct 18, 2016, at 7:01 AM, thib...@macports.org wrote: > > > > Revision > > 154019 > > Author > > thib...@macports.org > > Date > > 2016-10-18 05:01:47 -0700 (Tue, 18 Oct 2016) > > Log Message > > > > LORENE: fix archflags in debug builds, remove -lX11 from LIB_PGPLOT, add > usagenotes. > > Modified Paths > > > > • trunk/dports/science/LORENE/Portfile > > • trunk/dports/science/LORENE/files/local_settings > > > > +notes " > > ++--- LORENE Usage note ------------------------------ > ----------------------- > > +| To compile LORENE code, you should run: > > +| export HOME_LORENE=${prefix}/lib/lorene > > +| Codes are provided in \$HOME_LORENE/Codes. To use them, copy them to > some > > +| place were your have write access. > > ++---------------------------------------------------------- > ----------------- > > I'm not in favor of ASCII art boxes in notes. Just put the text; let > MacPorts line wrap and format it. If you believe MacPorts is not displaying > the notes prominently enough, then making notes more prominent by using > boxes or whatever should be done in MacPorts base, not in each individual > port. > > > > _______________________________________________ > macports-dev mailing list > macports-dev@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-dev >
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev