> > + mv ${PREFIX}/share/crawl/docs ${PREFIX}/share/doc/crawl
>
> The txt files are loaded by the program, see various things in
> command.cc, so I think they may need to stay where they were
Good catch. Using documentation outside of the projects source root
as source code wasn't something that
> + mv ${PREFIX}/share/crawl/docs ${PREFIX}/share/doc/crawl
The txt files are loaded by the program, see various things in
command.cc, so I think they may need to stay where they were
> On 17 April 2025 08:44:50 Stuart Henderson wrote:
>
> yes it is correct to use LOCALBASE for "files from other ports", I wouldn't
> have said it otherwise.
>
> PREFIX is just for where files from this port should be installed.
Right, I understand now. I was focusing too much on the expanded
v
yes it is correct to use LOCALBASE for "files from other ports", I wouldn't
have said it otherwise.
PREFIX is just for where files from this port should be installed.
--
Sent from a phone, apologies for poor formatting.
On 17 April 2025 06:12:34 Stefan Moran wrote:
On 2025/04/14 07:11, Stu
On 2025/04/14 07:11, Stuart Henderson wrote:
> On 2025/04/13 02:12, Stefan Moran wrote:
> > Substitute LOCALBASE with PREFIX, saves some horizontal
> > room.
>
> That's not correct, they're gor different things. PREFIX is for where
> files from this port should be installed, LOCALB
On 2025/04/13 02:12, Stefan Moran wrote:
> Substitute LOCALBASE with PREFIX, saves some horizontal
> room.
That's not correct, they're gor different things. PREFIX is for where
files from this port should be installed, LOCALBASE is for files from
dependencies etc.
> Instea
