From: Emanuel Haupt on
Hi

I was wondering if you're working on a port for the 64bit version of
the new beta state nvidia driver [1].

Since it's a completely different version it should IMO be seperate from
x11/nvidia-driver. Maybe x11/nvidia-driver-amd64 and x11/nvidia-driver
could be renamed to x11/nvidia-driver-i386.

Emanuel

[1] http://www.nvnews.net/vbulletin/showthread.php?t=142120
_______________________________________________
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: Alexey Dokuchaev on
On Fri, Dec 04, 2009 at 03:47:24PM +0100, Emanuel Haupt wrote:
> Hi
>
> I was wondering if you're working on a port for the 64bit version of
> the new beta state nvidia driver [1].

Yup, thanks for the pointer. I'm considering options right now.

>
> Since it's a completely different version it should IMO be separate from
> x11/nvidia-driver. Maybe x11/nvidia-driver-amd64 and x11/nvidia-driver
> could be renamed to x11/nvidia-driver-i386.

This would be the easiest route, but I'm not sure this is the best thing
to do. From user's perspective, one should be able to "cd
category/port" and "make install". The rest (including taking care of
architecture-dependent things) should be handled by underlying
infrastructure. Right now I believe our bpm is capable of the task, and
my pmake/bpm-fu is strong enough, we'll see.

../danfe
_______________________________________________
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: Rainer Hurling on
On 04.12.2009 16:18 (UTC+1), Alexey Dokuchaev wrote:
> On Fri, Dec 04, 2009 at 03:47:24PM +0100, Emanuel Haupt wrote:
>> Hi
>>
>> I was wondering if you're working on a port for the 64bit version of
>> the new beta state nvidia driver [1].
>
> Yup, thanks for the pointer. I'm considering options right now.
>
>> Since it's a completely different version it should IMO be separate from
>> x11/nvidia-driver. Maybe x11/nvidia-driver-amd64 and x11/nvidia-driver
>> could be renamed to x11/nvidia-driver-i386.
>
> This would be the easiest route, but I'm not sure this is the best thing
> to do. From user's perspective, one should be able to "cd
> category/port" and "make install". The rest (including taking care of
> architecture-dependent things) should be handled by underlying
> infrastructure. Right now I believe our bpm is capable of the task, and
> my pmake/bpm-fu is strong enough, we'll see.

I tried it with patching your Makefile and distinfo. In Makefile I only
changed DISTVERSION and DISTNAME and commented out ONLY_FOR_ARCHS.

It installs fine and as far as I can see now all is well :-)

This is on 9.0-CURRENT (amd64) from today.

Rainer Hurling

> ./danfe

_______________________________________________
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: Emanuel Haupt on
> On Fri, Dec 04, 2009 at 03:47:24PM +0100, Emanuel Haupt wrote:
> > Hi
> >
> > I was wondering if you're working on a port for the 64bit version of
> > the new beta state nvidia driver [1].
>
> Yup, thanks for the pointer. I'm considering options right now.
>
> >
> > Since it's a completely different version it should IMO be separate
> > from x11/nvidia-driver. Maybe x11/nvidia-driver-amd64 and
> > x11/nvidia-driver could be renamed to x11/nvidia-driver-i386.
>
> This would be the easiest route, but I'm not sure this is the best
> thing to do. From user's perspective, one should be able to "cd
> category/port" and "make install". The rest (including taking care of
> architecture-dependent things) should be handled by underlying
> infrastructure. Right now I believe our bpm is capable of the task,
> and my pmake/bpm-fu is strong enough, we'll see.

Right, you can put shared make functionality in a seperate file and
include it by both ports. Personally I'd prefer two seperate ports
rather than OPTIONS because the two drivers don't provide the same
funcionality (ie missing TRIM support) and have different versions.

Emanuel
_______________________________________________
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: Alexey Dokuchaev on
On Fri, Dec 04, 2009 at 04:32:11PM +0100, Emanuel Haupt wrote:
> > On Fri, Dec 04, 2009 at 03:47:24PM +0100, Emanuel Haupt wrote:
> > > Hi
> > >
> > > I was wondering if you're working on a port for the 64bit version of
> > > the new beta state nvidia driver [1].
> >
> > Yup, thanks for the pointer. I'm considering options right now.
> >
> > >
> > > Since it's a completely different version it should IMO be separate
> > > from x11/nvidia-driver. Maybe x11/nvidia-driver-amd64 and
> > > x11/nvidia-driver could be renamed to x11/nvidia-driver-i386.
> >
> > This would be the easiest route, but I'm not sure this is the best
> > thing to do. From user's perspective, one should be able to "cd
> > category/port" and "make install". The rest (including taking care of
> > architecture-dependent things) should be handled by underlying
> > infrastructure. Right now I believe our bpm is capable of the task,
> > and my pmake/bpm-fu is strong enough, we'll see.
>
> Right, you can put shared make functionality in a separate file and
> include it by both ports. Personally I'd prefer two separate ports
> rather than OPTIONS because the two drivers don't provide the same
> functionality (ie missing TRIM support) and have different versions.

In any case, I'll post a diff here for review before I make any commits
WRT amd64 support in nvidia-driver.

../danfe
_______________________________________________
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"