On Sat, Mar 13, 2010 at 08:40:32PM -0500, jhell wrote:
> Rather simple way to go about creating final packages and from some
> earlier emails to the list there was word of some directories not being
> included in final built packages due to empty directories or something
> like that so be carefu
On Sat, 13 Mar 2010 23:31, xorquewasp@ wrote:
'Lo,
On 2010-03-13 20:40:32, jhell wrote:
Not that this is a solution to your problem but it might be a possibility
for you to consider, but a couple years back I dropped using make
package(-recursive) and just scripted out making backup packages u
'Lo,
On 2010-03-13 20:40:32, jhell wrote:
> Not that this is a solution to your problem but it might be a possibility
> for you to consider, but a couple years back I dropped using make
> package(-recursive) and just scripted out making backup packages using
> something like the following.
I p
On Sat, 13 Mar 2010 02:52, xorquewasp@ wrote:
Have you tried just setting PORTSDIR and letting bsd.port.mk set the
rest of the paths with their defaults that are relative to PORTSDIR? If
that works, then we can start hunting for places that are not handling
absolute vs. relative paths correctly
On Sat, Mar 13, 2010 at 11:51 AM, Garrett Cooper wrote:
> On Fri, Mar 12, 2010 at 11:52 PM, wrote:
>>> Have you tried just setting PORTSDIR and letting bsd.port.mk set the
>>> rest of the paths with their defaults that are relative to PORTSDIR? If
>>> that works, then we can start hunting for p
On Fri, Mar 12, 2010 at 11:52 PM, wrote:
>> Have you tried just setting PORTSDIR and letting bsd.port.mk set the
>> rest of the paths with their defaults that are relative to PORTSDIR? If
>> that works, then we can start hunting for places that are not handling
>> absolute vs. relative paths cor
> Have you tried just setting PORTSDIR and letting bsd.port.mk set the
> rest of the paths with their defaults that are relative to PORTSDIR? If
> that works, then we can start hunting for places that are not handling
> absolute vs. relative paths correctly in bsd.port.mk.
Now, with only:
PORT
On 2010-03-12 22:36:54, Greg Larkin wrote:
> Hi xw,
>
> I noticed something strange here. How is WRKDIR (in this case
> "/var/ports/work/var/ports/tree/devel/eggdbus/work") defined? It looks
> like bsd.port.mk combined your WRKDIRPREFIX and PORTSDIR to create that
> path, but skimming the code,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
xorquew...@googlemail.com wrote:
[...]
> DISTDIR= /var/ports/distfiles
> PACKAGES= /var/ports/packages
> WRKDIRPREFIX= /var/ports/work
> PORTSDIR= /var/ports/tree
>
> jail# vi /etc/profile
> FTP_PASSIVE_MODE=yes
> HTTP_PROXY=10.1.3.3:
This is a complete lot of how to reproduce the various errors I've
seen with 'make package-recursive'. I've checked the pointyhat logs
and there are no errors logged for the packages involved here. There
seems to be a bug somewhere in ports. I've used inkscape as a scapegoat
here but the errors occ
10 matches
Mail list logo
