RFS: min12xxw
Dear mentors, I am looking for a sponsor for my package "min12xxw". * Package name: min12xxw Version : 0.0.9-1 Upstream Author : Manuel Schiller <[EMAIL PROTECTED]> * URL : http://www.hinterbergen.de/mala/min12xxw/ * License : GPL Section : graphics It builds these binary packages: min12xxw - Printer driver for KonicaMinolta PagePro 1[234]xxW The package is lintian clean. The upload would fix these bugs: 334093 (ITP) The package can be found on mentors.debian.net at http://mentors.debian.net/debian/pool/main/m/min12xxw Or just "apt-get source min12xxw" if your sources.list contains: deb-src http://mentors.debian.net/debian unstable main contrib non-free I would be glad if someone uploaded this package for me. The package is maintained in the collab-maint svn at svn.debian.org/svn/collab-maint/ext-maint/min12xxw Co-maintainers welcome, but not needed, since min12xxw is a very small package, which doesn't cause lots of work. Upstream is active and responsive :). Please CC me, as I'm not (yet) on the list. Kind regards Stefan Potyra pgppiLgr0StFO.pgp Description: PGP signature
Re: library files in package
George Danchev <[EMAIL PROTECTED]> writes: > On Wednesday 19 July 2006 17:26, Steven Hill wrote: >> Is there a way to include library files in a package and have them >> installed automatically in /usr/lib, > > Yes, you can have binary package installing files whereever you want, but you > must comply with what Filesystem Hierarchy Standard says about the items > involved. Also with policy which forbids shipping public binaries (i.e. /usr/bin/ stuff) and shared libraries in the same package. If you do that you will promply get a bugreport on your package from me. >> or failing that is there a way to >> have a package automatically install a package that the app being >> installed depends on? > > Of course. That is packaging system front ends job (apt-get, aptitude, > dselect...). Please check Debian Policy about what binary and source packages > are for, and how the relationships between packages are being managed. A depends is the correct waz for this problem. All library packages in debian do it this way. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: library files in package
On Wednesday 19 July 2006 17:26, Steven Hill wrote: > Is there a way to include library files in a package and have them > installed automatically in /usr/lib, Yes, you can have binary package installing files whereever you want, but you must comply with what Filesystem Hierarchy Standard says about the items involved. > or failing that is there a way to > have a package automatically install a package that the app being > installed depends on? Of course. That is packaging system front ends job (apt-get, aptitude, dselect...). Please check Debian Policy about what binary and source packages are for, and how the relationships between packages are being managed. > Any help would be greatly appreciated - thank you Finally, if you want to go for packaging libraries you should read libpkg-guide[1], which explains the issues involved wrt libraries: [1] http://www.netfort.gr.jp/~dancer/column/libpkg-guide/ -- pub 4096R/0E4BD0AB 2003-03-18 fingerprint 1AE7 7C66 0A26 5BFF DF22 5D55 1C57 0C89 0E4B D0AB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: library files in package
Steven Hill <[EMAIL PROTECTED]> wrote: >>From what I have seen, unsatisfied dependencies that are listed in the > Depends: section just cause the installation to abort and warn the user > of the unsatisfied dependency - am I missing something? That is going to happen if you install the package with "dpkg -i". > I would like the > missing dependency to be satisfied automatically by the installer by > invoking "apt-get install" or some similar process... apt-get, aptitude and friends will do that automatically. Never noticed it? Regards, Frank -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
Re: library files in package
On Thu, Jul 20, 2006 at 08:27:34AM +0200, Frank B. Brokken wrote: Hi Frank, nice to see you here. :-) What you say is correct, but I want to change the wording a bit to avoid confusion: > You'll find examples of that in all debian library packages. It's not very > different from making a binary package. The change I'm making is "a binary package" -> "any other binary package". What Debian calls a "binary package" is the thing that gets installed by the user, independent of what's in it. It usually ends in .deb (or .udeb for installer binary packages). There are two kinds of packages, "binary" and "source". So even a pure documentation package with only text files in it is called a "binary package". The library packages you talk about are binary packages as well (and of course they also have a source package). Thanks, Bas Wijnen -- I encourage people to send encrypted e-mail (see http://www.gnupg.org). If you have problems reading my e-mail, use a better reader. Please send the central message of e-mails as plain text in the message body, not as HTML and definitely not as MS Word. Please do not use the MS Word format for attachments either. For more information, see http://129.125.47.90/e-mail.html signature.asc Description: Digital signature
