Prev: Sourceforge has changed?
Next: ���j�٦�`�j��3P����ˬ۫�
From: Paul Schmehl on 22 Jul 2010 17:03
I'm trying to update the devel/byaccj port, which I maintain. The new version
has made some subtle changes in naming, which have thrown me for a loop;

PORTNAME= byaccj
PORTVERSION= 1.15
DISTFILES= byaccj1.15_src.tar.gz

WRKDIR is work/byaccj1.15 when the files are extracted.

If I don't define WRKSRC, it's byaccj-1.15. If I define it as
${PORTNAME}${PORTVERSION}, it's still byaccj-1.15. Hardcoding it doesn't seem
like the right answer, but what is?

--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
*******************************************
"It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead." Thomas Jefferson

_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Greg Larkin on 22 Jul 2010 18:00
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul Schmehl wrote:
> I'm trying to update the devel/byaccj port, which I maintain. The new
> version has made some subtle changes in naming, which have thrown me for
> a loop;
>
> PORTNAME= byaccj
> PORTVERSION= 1.15
> DISTFILES= byaccj1.15_src.tar.gz
>
> WRKDIR is work/byaccj1.15 when the files are extracted.
>
> If I don't define WRKSRC, it's byaccj-1.15. If I define it as
> ${PORTNAME}${PORTVERSION}, it's still byaccj-1.15. Hardcoding it
> doesn't seem like the right answer, but what is?
>

Hi Paul,

I didn't have a problem downloading the 1.15 distfile from SF (ref: your
other message) nor setting WRKSRC to the correct value. Please check my
Makefile diff here, and let me know if it works for you or not.

http://people.freebsd.org/~glarkin/diffs/byaccj-Makefile.diff

The build immediately fails, though, because the distro Makefile has
some MacOSX-specific stuff in it. I presume that's what you're working
on fixing in the port update.

Hope that helps,
Greg
- --
Greg Larkin

http://www.FreeBSD.org/ - The Power To Serve
http://www.sourcehosting.net/ - Ready. Set. Code.
http://twitter.com/sourcehosting/ - Follow me, follow you
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFMSL+A0sRouByUApARAvcGAJ919ZZGIio5ioJ82ObCcd+mwtzHUwCdHTYP
W+mULbeNyOcLbJCOKAVE/M8=
=LyQ9
-----END PGP SIGNATURE-----

_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Paul Schmehl on 22 Jul 2010 18:44
--On Thursday, July 22, 2010 18:00:32 -0400 Greg Larkin <glarkin(a)FreeBSD.org>
wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Paul Schmehl wrote:
>> I'm trying to update the devel/byaccj port, which I maintain. The new
>> version has made some subtle changes in naming, which have thrown me for
>> a loop;
>>
>> PORTNAME= byaccj
>> PORTVERSION= 1.15
>> DISTFILES= byaccj1.15_src.tar.gz
>>
>> WRKDIR is work/byaccj1.15 when the files are extracted.
>>
>> If I don't define WRKSRC, it's byaccj-1.15. If I define it as
>> ${PORTNAME}${PORTVERSION}, it's still byaccj-1.15. Hardcoding it
>> doesn't seem like the right answer, but what is?
>>
>
> Hi Paul,
>
> I didn't have a problem downloading the 1.15 distfile from SF (ref: your
> other message) nor setting WRKSRC to the correct value. Please check my
> Makefile diff here, and let me know if it works for you or not.
>
> http://people.freebsd.org/~glarkin/diffs/byaccj-Makefile.diff
>
> The build immediately fails, though, because the distro Makefile has
> some MacOSX-specific stuff in it. I presume that's what you're working
> on fixing in the port update.
>

Thanks to your help I spotted my error and fixed it. I'm about ready to submit
the update. It's amazing how often I can look at something and not see it. :-(

The Sourceforge situation is a mess, though. I'm going to have to wait for
that to get fixed in the macros before I can proceed with afterglow.

--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
*******************************************
"It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead." Thomas Jefferson

_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Sahil Tandon on 22 Jul 2010 21:55
On Thu, 2010-07-22 at 17:44:44 -0500, Paul Schmehl wrote:

[ .. ]

> The Sourceforge situation is a mess, though. I'm going to have to
> wait for that to get fixed in the macros before I can proceed with
> afterglow.

Please provide some evidence about the brokenness of the SF macros.

--
Sahil Tandon <sahil(a)FreeBSD.org>
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

 | 
Pages: 1
Prev: Sourceforge has changed?
Next: ���j�٦�`�j��3P����ˬ۫�