Re: LPRng Spec File?

David, I maintain the LPRng and IFHP packages locally (I haven't been able to drum up enough interest among the OpenPKG fellows to get it into the repository). These probably need a little bit of tweaking for 2.0 compatibility--I last updated them a couple of months ago. The specs are at: http:

SPIN package submitted

there any interest in incorporating this into the OpenPKG archives? -- Matt Hoosier UNIX Administrator / Accounts Manager CIS Department, Kansas State University signature.asc Description: This is a digitally signed message part

Release engineering; unresolved package problems

ame of the index files created by 'genbasedir'. The server-side expects one filename, and the client programs expect another. -- Matt Hoosier UNIX Administrator / Accounts Manager Department of Computing and Information Sciences Kansas State University signature.asc Description: This i

Re: 'pine' source package uploaded

Nevermind about this one; looks like a 'pine' package was just added to the repository today. On Mon, 2003-09-15 at 20:40, Matt Hoosier wrote: > Hi, > > The follow up on the earlier exchange of messages, I've put together a > package for the 'pine' emai

'pine' source package uploaded

Hi, The follow up on the earlier exchange of messages, I've put together a package for the 'pine' email client. It's sitting in the contrib directory on the FTP site. --Matt -- Matt Hoosier UNIX Administrator / Accounts Manager Department of Computing and Information S

[OpenPKG #255] [apt] patches for compatibility with openpkg >= 20030913

to a patch was a little too recursive for me to think about... --Matt Matt Hoosier CIS Accounts Manager Kansas State University <[EMAIL PROTECTED]> ## ## apt.spec -- OpenPKG RPM Specification ## Copyright (c) 2000-2003 The OpenPKG Project <http://www.openpkg.org/> ## Copyright (c)

pine licensing?

licensing terms are compatible, I have a 'pine' package that I would like to contribute. -- Matt Hoosier UNIX Administrator / Accounts Manager Department of Computing and Information Sciences Kansas State University signature.asc Description: This is a digitally signed message part

'apt' package available

e the OpenPKG maintainers: how else may I be of assistance to help this package be adopted into the CVS repository? -- Matt Hoosier UNIX Administrator / Accounts Manager Department of Computing and Information Sciences Kansas State University signature.asc Description: This is a digitally signed message part

lprng / ifhp packaged

I've packaged LPRng and the corresponding print filter, ifhp. Is there any interesting in integrating these into the main distribution? -- Matt Hoosier CIS Accounts Manager Kansas State University # package information Name: ifhp Summary:Printer filter for HP Las

Re: Patches to python under Solaris

This newer upstream release of python solved the problem. Thanks. On Sat, 2003-05-31 at 06:15, Ralf S. Engelschall wrote: > On Tue, May 27, 2003, Matt Hoosier wrote: > > > It seems that when built on Solaris, the python package is missing the > > contents of "/cw/li

Patches to python under Solaris

ition of the CC, CXX, CFLAGS, and CXXFLAGS that cause the build to omit these loadable libraries, for whatever reason. The attached patch to python.spec omits those environment variables when the package is built on Solaris. -- Matt Hoosier CIS Accounts Manager Kansas State University --- python.

[BugDB] mozilla 1.3's nspr doesn't build on Solaris (PR#175)

Full_Name: Matt Hoosier Version: openpkg 20030324, mozilla 20030316 OS: SunOS 5.9 Submission from: (NULL) (129.130.10.83) The NSPR bundled with Mozilla (1.3) doesn't build on the Sun platform. Configuration succeeds, but compilation fails when an attempted link is aborted claiming that the

[BugDB] Config file location wrong in libxml (PR#172)

Full_Name: Matt Hoosier Version: OS: Solaris 9 / UltraSparc Submission from: (NULL) (129.130.10.83) The libxml package seems to be compiled with the expectation that config file are found under /etc/sgml (rather than the correct %{l_prefix}/etc/sgml). This seems to be a bug in the upstream