Bug 26313

Summary: New Port: german/eagle: A tool for designing printed circuit boards
Product: Ports & Packages Reporter: neuf <neuf>
Component: Individual Port(s)Assignee: Ade Lovett <ade>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
file.shar none

Description neuf 2001-04-03 12:40:01 UTC 
This is a port of EAGLE (Easily Applicable Graphical Layout Editor).
The program consists of three main modules: Layout Editor, Schematic Editor 
and Autorouter. These are embedded in a single user interface. Therefore there
is no need for converting netlists between schematics and layouts.
Comment 1 Will Andrews freebsd_committer freebsd_triage 2001-04-07 07:00:28 UTC 
State Changed
From-To: open->analyzed

Umm.  This doesn't seem to be working for me..: 

===>  Installing for eagle-4.01 
===>   eagle-4.01 depends on file: /compat/linux/etc/redhat-release - found 
/bin/mkdir -p /compat/linux/opt/eagle 
Please ignore the following error message line 
rpm:No such file or directory 
*** Error code 1 (ignored) 
./install: not found 
*** Error code 127 

Stop in /net/puck/will/ports/german/eagle. 
*** Error code 1 

And that's after I added this line: 

${MKDIR} ${PREFIX}/opt/eagle 

to your custom do-install target.
Comment 2 Will Andrews 2001-04-09 18:39:16 UTC 
On Mon, Apr 09, 2001 at 05:12:39PM +0200, Harald Neuffer wrote:
> probably the wrong way to write directly to you instead using the GNATS
> database. But I don't know whether I can answer direct to an existing PR
> via the send-pr cgi script.

You can use a regular mailer, and cc: to FreeBSD-gnats-submit@FreeBSD.org.

> Now to the problem. During the develop of the port eagle, I used a
> system where the linux_base was installed from the ports. This port
> requires the rpm port. Thus I thought, if I need 'rpm' to install a my
> rpm package, I need only check whether the linux_base port is installed
> or not. You are probably not using the port version, but the package of
> the linux_base and there is no rpm package installation before, thus
> installing the port eagle will fail because there is no 'rpm'.

That would not be linux_base's fault.  BUILD_DEPENDS is only valid for
the build target.  It doesn't work for any other target.

> --- Makefile.orig       Mon Apr  9 15:10:28 2001
> +++ Makefile    Mon Apr  9 14:16:49 2001
> @@ -18,6 +18,7 @@
>  
>  USE_LINUX=	yes
>  USE_LINUX_PREFIX=	yes
> +RUN_DEPENDS=	rpm:${PORTSDIR}/archivers/rpm
>  
>  NO_PACKAGE=	yes
>  NO_BUILD=	yes

I believe your solution is correct, too.

-- 
wca
Comment 3 neuf 2001-04-23 09:56:59 UTC 
Will Andrews wrote:
> 
> On Mon, Apr 09, 2001 at 05:12:39PM +0200, Harald Neuffer wrote:
> > probably the wrong way to write directly to you instead using the GNATS
> > database. But I don't know whether I can answer direct to an existing PR
> > via the send-pr cgi script.
> 
> You can use a regular mailer, and cc: to FreeBSD-gnats-submit@FreeBSD.org.
> 
> > Now to the problem. During the develop of the port eagle, I used a
> > system where the linux_base was installed from the ports. This port
> > requires the rpm port. Thus I thought, if I need 'rpm' to install a my
> > rpm package, I need only check whether the linux_base port is installed
> > or not. You are probably not using the port version, but the package of
> > the linux_base and there is no rpm package installation before, thus
> > installing the port eagle will fail because there is no 'rpm'.
> 
> That would not be linux_base's fault.  BUILD_DEPENDS is only valid for
> the build target.  It doesn't work for any other target.
> 
> > --- Makefile.orig       Mon Apr  9 15:10:28 2001
> > +++ Makefile    Mon Apr  9 14:16:49 2001
> > @@ -18,6 +18,7 @@
> >
> >  USE_LINUX=   yes
> >  USE_LINUX_PREFIX=    yes
> > +RUN_DEPENDS= rpm:${PORTSDIR}/archivers/rpm
> >
> >  NO_PACKAGE=  yes
> >  NO_BUILD=    yes
> 
> I believe your solution is correct, too.
> 
> --
> wca
Hi,

I'm a little uncertain, whether you need more things from me that EAGLE
will become a port or not. The state of PR ports/26313 is still
analysed. Or is the port on the way?

Thanks,

the impatient Harald
Comment 4 Ade Lovett freebsd_committer freebsd_triage 2002-04-13 04:12:16 UTC 
State Changed
From-To: analyzed->closed

It's still broken, a year later.  Byebye.
Comment 5 Ade Lovett freebsd_committer freebsd_triage 2002-04-13 04:12:16 UTC 
Responsible Changed
From-To: freebsd-ports->ade

My fault[tm]