Bug 17036 - working port for arla-0.31
Summary: working port for arla-0.31
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-ports (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-02-28 06:20 UTC by assar
Modified: 2000-03-04 22:05 UTC (History)
1 user (show)

See Also:


Attachments
file.diff (3.55 KB, patch)
2000-02-28 06:20 UTC, assar
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description assar 2000-02-28 06:20:01 UTC
The current arla port is based on (old) arla 0.28 and does not build
on 4.0-current.  This update fixes both of these problems.  I've sent
in earlier patches to which nothing happened, they were assigned to
the maintainer (thepish).  As far as I can tell, the maintainer does
not have time to deal with this.

I would appreciate it a lot if this can be applied so that 4.0 gets
shipped with a working arla.  Feel free to send any questions to me.

How-To-Repeat: 
cd /usr/ports/net/arla && make
Comment 1 assar 2000-03-03 13:11:09 UTC
I wrote:
> Will Andrews <andrews@technologist.com> writes:
> > About time! I was pretty intent on submitting a port removal request for
> > this particular port, since I've never seen it build successfully before.
> 
> Thanks.  Having it there but not building didn't make me very happy
> either...

Sorry for being somewhat insistent on this, but I would like this to
be fixed before the freeze on March 8th.  So, what more is there's to
do on this and want can I do to make sure it happens?

The patches in ports/17036 should make everything build just fine.  If
there are any issues with those, please tell me and I'll try to solve
them.  Otherwise, just commit it. :-)

/assar
Comment 2 kris 2000-03-03 21:48:20 UTC
I'll try and commit this over the weekend. I wanted to just confirm it
builds, which required me to install kerberos first :)

Kris

On 3 Mar 2000 assar@stacken.kth.se wrote:

> I wrote:
> > Will Andrews <andrews@technologist.com> writes:
> > > About time! I was pretty intent on submitting a port removal request for
> > > this particular port, since I've never seen it build successfully before.
> > 
> > Thanks.  Having it there but not building didn't make me very happy
> > either...
> 
> Sorry for being somewhat insistent on this, but I would like this to
> be fixed before the freeze on March 8th.  So, what more is there's to
> do on this and want can I do to make sure it happens?
> 
> The patches in ports/17036 should make everything build just fine.  If
> there are any issues with those, please tell me and I'll try to solve
> them.  Otherwise, just commit it. :-)
> 
> /assar
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-ports" in the body of the message
> 

----
In God we Trust -- all others must submit an X.509 certificate.
    -- Charles Forsythe <forsythe@alum.mit.edu>
Comment 3 Kris Kennaway freebsd_committer freebsd_triage 2000-03-04 22:05:31 UTC
State Changed
From-To: open->closed

Upgrade committed.