On Wed, May 22, 2013 at 02:21:43PM +0100, Stuart Henderson wrote:
> On 2013/05/22 14:13, David Coppa wrote:
> > On Wed, May 22, 2013 at 2:08 PM, Stuart Henderson <[email protected]> wrote:
> > > On 2013/05/22 13:47, David Coppa wrote:
> > >>
> > >> Hi!
> > >>
> > >> Since the new awesome-3.5.1 will use the lua-5.2 flavor of some lua
> > >> ports, should I add them explicitly to devel/Makefile, like in the
> > >> diff below?
> > >
> > > As long as they don't conflict when installed, yep.
>
> I'll expand on this. Unless something is in the initial stages of
> "import but don't link yet", or there are special circumstances
> e.g. conflicting dependencies, all flavours should get listed in
> subdirectory Makefiles. Without this, they don't get included in
> sqlports/INDEX so people don't find them when they're searching
> for ports depending on another port.
I'll take care of adding all the lua52 flavors to the Makefiles next week.
> > >> TIA,
> > >> David
> > >>
> > >> Index: Makefile
> > >> ===================================================================
> > >> RCS file: /cvs/ports/devel/Makefile,v
> > >> retrieving revision 1.1132
> > >> diff -u -p -u -p -r1.1132 Makefile
> > >> --- Makefile 22 May 2013 11:00:29 -0000 1.1132
> > >> +++ Makefile 22 May 2013 11:37:08 -0000
> > >> @@ -400,14 +400,18 @@
> > >> SUBDIR += lua-cjson
> > >> SUBDIR += lua-cmsgpack
> > >> SUBDIR += lua-lgi
> > >> + SUBDIR += lua-lgi,lua52
> > >
> > > I see it's not new, but ugh at the use of FULLPKGNAME in PLIST for
> > > some of these ports.. ;)
> >
> > I'd like to have some suggestions on how to handle these.
> >
> > How to not use FULLPKGNAME and have both flavors (lua51 and lua52)
> > concurrently installed without conflicts?
> >
>
> python.port.mk has MODPY_PY_PREFIX for this, so ports can use
> share/doc/${MODPY_PY_PREFIX}-foo which translates to py-foo or py3-foo.
We can use MODLUA_PREFIX for this, which I'll then set to _MODLUA_PKG_PREFIX.
--
Cheers,
Jasper
"Stay Hungry. Stay Foolish"
