Re: A question about debconf
Feifei Jia <[EMAIL PROTECTED]> wrote: > Hi there, > > I wanted to delete the date which stored in debconf database when > purge a package. So I added "db_purge" both in prerm and postrm > scripts, but it seemed not work. > > Did I miss something? Any hints appreciated. Did you load confmodule? Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
Re: RFS: ksudoku -- sudoku puzzle generator/solver
On Thursday 10 November 2005 18:50, Ryan Schultz wrote: > * Package name: ksudoku > Version : 0.3 > Upstream Author : Francesco Rossi <[EMAIL PROTECTED]> > * URL : http://ksudoku.sourceforge.net > * License : GPL > Description : sudoku puzzle generator/solver > > KSudoku is an interface for creating and solving sudoku puzzles, which > are grid-based placement puzzles that require time and logic to solve. > KSudoku is able to work with both 2D and 3D versions of these puzzles, > in grids of any square layout up to 25x25. It can also generate > configurable symmetric puzzles and other special types. > > Documentation is relicensed under the GPL; see debian/copyright. > > lintian/pbuilder-clean packages available from: > deb http://rschultz.ath.cx/debian unstable/i386/ > deb-src http://rschultz.ath.cx/debian unstable/source/ I'm generally willing to sponsor this package. Thoughts: - The orig.tar.gz differs from the upstream tarball. It's just a rename of the directory inside and the admin/CVS directory is removed. It's a religious issue but I would rather leave the original upstream archive intact. The CVS wouldn't show up in the final package anyway. - You patched ksudoku-0.3/doc/en/index.docbook. Would that be better solved through dpatch? - The debian/copyright lacks the years of copyright. - A 'desktop' file would be nice in addition to the 'menu' file. (Don't forget to call dh_desktop.) - Some debhelper calls (like dh_link) are not needed. - Could you send the manpages upstream so they can be included in the orig.tar.gz at the next release? - The AUTHOR section of the man pages looks strange to me. Christoph -- ~ ~ ".signature" [Modified] 1 line --100%--1,48 All -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: A question about debconf
On 11/11/05, Frank Küster <[EMAIL PROTECTED]> wrote: > Feifei Jia <[EMAIL PROTECTED]> wrote: > > > Hi there, > > > > I wanted to delete the date which stored in debconf database when > > purge a package. So I added "db_purge" both in prerm and postrm > > scripts, but it seemed not work. > > > > Did I miss something? Any hints appreciated. > > Did you load confmodule? > > Regards, Frank > -- > Frank Küster > Inst. f. Biochemie der Univ. Zürich > Debian Developer > Yes, I did add ". /usr/share/debconf/confmodule" at the beginning of the script. -- Thanks~
Re: RFC: libinieditor-java
On 11/10/05, Wolfgang Baer <[EMAIL PROTECTED]> wrote: > (1) > Architecture: any > > Java packages are Architecture: all ! This change will also mean to > use Build-Depends-Indep and to move the build stuff into the > binary-indep: target in the debian/rules file. Done. > (2) > Depends: gij | kaffe | sablevm | java1-runtime | java2-runtime > > IMHO its enough to depend on one concrete java1-runtime and most > packages in debian use kaffe there (but thats a personal viewpoint) > > Depends: kaffe | java1-runtime | java2-runtime Done. I've also changed the dependency to kaffe (>=2:1.1.5) as suggested. The package is lintian and linda-clean and has been successfully rebuilt with pbuilder. If anyone has time to look at my revised package, it can be located at http://deathwing.penarmac.com/debian/libinieditor-java/. If a DD thinks that the package is okay, I would also like to request for a sponsored upload. Thank you very much. -- GPG Key ID: 0xD6655C18 Linux Just Simply Rocks! http://deathwing.penarmac.com/
Re: Package that depends on ming
Thanks for all the clues. I'll continue the thread on http://bugs.debian.org/295760 to see if we can get libming going on, and my package too (BTW my package is op-panel [1]). [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=323689 El jue, 10-11-2005 a las 16:06 +1100, Aníbal Monsalve Salazar escribió: > On Thu, Nov 10, 2005 at 12:29:27PM +0800, Paul Wise wrote: > >On Wed, 2005-11-09 at 21:08 +0100, Joost van Baal wrote: > > > >>>Since ming is not in Debian anymore, > >> > >>You're talking about libming, which is still supported in woody > >>(oldstable). Do you know why it didn't make it to sarge? It might be > >>possible to get it re-enter Debian. (Just saw upstream released 0.3.0, > >>which never was shipped with Debian.) > > Mattias Nordstrom is trying to get it back in unstable. > > See http://bugs.debian.org/295760 > > >From http://ftp-master.debian.org/removals.txt > > > >[Date: Mon, 12 Jan 2004 22:30:29 -0500] [ftpmaster: James Troup] > >Removed the following packages from unstable: > > > > libming | 0.2a.cvs20030716-2 | source, alpha, arm, hppa, i386, ia64, > > m68k, mips, mipsel, powerpc, s390, sparc > >libming-dev | 0.2a.cvs20030716-2 | alpha, arm, hppa, i386, ia64, m68k, mips, > >mipsel, powerpc, s390, sparc > >libming-fonts-openoffice | 0.1-2 | source, all > >libming-util | 0.2a.cvs20030716-2 | alpha, arm, hppa, i386, ia64, m68k, > >mips, mipsel, powerpc, s390, sparc > >libswf-perl | 0.2a.cvs20030716-2 | alpha, arm, hppa, i386, ia64, m68k, mips, > >mipsel, powerpc, s390, sparc > > php4-ming | 0.2a.cvs20030716-2 | alpha, arm, hppa, i386, ia64, m68k, mips, > > mipsel, powerpc, s390, sparc > >python2.1-ming | 0.2a.cvs20030716-2 | alpha, arm, hppa, i386, ia64, m68k, > >mips, mipsel, powerpc, s390, sparc > >python2.2-ming | 0.2a.cvs20030716-2 | alpha, arm, hppa, i386, ia64, m68k, > >mips, mipsel, powerpc, s390, sparc > >Closed bugs: 166973 166990 > > > >--- Reason --- > >RoQA; orphaned, dead upstream, grave bugs, unused. > >-- > > > >Upstream CVS is slowly ticking over (last change 3 weeks ago), and if > >they make an actual release, I'll be adding ming to the list of osflash > >related packages to do on http://osflash.org/debian_packaging > > > >>>should the > >>>package be on the non-free section? > >> > >>If it _depends_ upon libming, your program can't be shipped with Debian > >>as long as libming is not in Debian. > > > >It can be shipped in contrib though. contrib is for free packages with > >dependencies (free or otherwise) that are not in debian. > > > >-- > >bye, > >pabs > > > >http://wiki.debian.org/PaulWise > > Aníbal Monsalve Salazar > -- > .''`. Debian GNU/Linux > : :' : Free Operating System > `. `' http://debian.org/ > `- http://v7w.com/anibal -- Alejandro Ríos Peña Ing. en Electrónica y Telecomunicaciones. Avatar ltda. Grupo GNU/Linux Universidad del Cauca - GLUC. Comunidad Debian-Colombia. signature.asc Description: This is a digitally signed message part
Re: sponsor quake3 quake3-data packages
On Wed, Nov 09, 2005 at 09:09:03AM +0100, Marc Leeman wrote: > Last week, I made packages for Quake III. For these, I used the work > great of Jamie, the quake II maintainer and adjusted it: the package is > split in quake3 and quake3-data. Do you know of any efforts to create DFSG q3a content, which would allow migration into main? (just curious) -- Jon Dowland http://jon.dowland.name/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: All files are in DESTDIR but non will be copied into the packages
Hi all, because I wasn't subscribed I answer with a completely new mail, now I am. Sorry for the confusion in the thread view of your email app. On Thu, Nov 10, 2005 at 07:25:35PM +0100, Timo Steuerwald wrote: Hi all, I try to create packages for sipX from sipfoundry.org. This is a PBX like asterisk and is composed of a few subprojects like sipXportLib, sipXtackLib... I now tried to create a package for sipXportLib. What I have done up to now: 1. Read http://www.debian.org/doc/maint-guide/ completely :-) 2. executed dh_make -e 3. filled files like copyright, control and so on with useful information 4. tried to build it via dpkg-buildpackage -rfakeroot This has completed successfully, but inside the packages data.tar.gz ins nearly empty. There exists only parts of the data that belongs to the debian subdirectory (like usr/share/doc/sipxportlib/copyright). No libs, nothing. The same for the -dev package: No documentation, include files and so on. If I look now to the debian subdirectory, there are three subdirectories tmp (which is my DESTDIR in the rules file), sipxportlib and sipxportlib-dev. The last two only contain the same files as in the packages. What can I do to add the files from DESTDIR to the two packages? - I thought .dirs and .files are handling this. If I understand your intent, you want the package to "make install" to ./debian/tmp/, and then you want *.dirs and *.files to copy them from that location to ./debian/package/, where they will be installed into the package. Right? Firstly, you should know that ./debian/tmp/ was the install directory for old versions of debhelper. Nowadays its ./debian/$package/. It shoulds like this is working the way it should be, but you should check that ./debian/dh_compat exists and contains a "4". Hmmh, $package doesn't work for me. I've searched the archive and have seen that DH_COMPAT should be IMHO a environment variable inside the rules file (e.g. http://lists.debian.org/debian-mentors/2001/04/msg00011.html). I have defined it and set to 4 Then you should make sure that ./debian/rules has dh_install uncommented; thats the program that accepts as input. Finally, the name of the input files are "*.install" and not "*.files" (which seems to be for old program dh_movefiles). Ok, I have uncommented dh_install and also renamed the files to *.install. Now, the content of the packages is as expected. DESTDIR still points to /debian/tmp, but this doesn't make any problems. Thanks for your help! :-) Cheers, Timo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: sponsor quake3 quake3-data packages
In gmane.linux.debian.devel.mentors, you wrote: >> Last week, I made packages for Quake III. For these, I used the work >> great of Jamie, the quake II maintainer and adjusted it: the package is >> split in quake3 and quake3-data. > > Do you know of any efforts to create DFSG q3a content, which would allow > migration into main? (just curious) There is, but it's in very early stage: http://www.planetgargoyle.com/openarena/ Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: All files are in DESTDIR but non will be copied into the packages
Timo Steuerwald: > >Timo Steuerwald: > >>I try to create packages for sipX from sipfoundry.org. This is a PBX > >>like asterisk and is composed of a few subprojects like sipXportLib, > >>sipXtackLib... > >>I now tried to create a package for sipXportLib. > >Firstly, you should know that ./debian/tmp/ was the install directory > >for old versions of debhelper. Nowadays its ./debian/$package/. It > >shoulds like this is working the way it should be, but you should > >check that ./debian/dh_compat exists and contains a "4". > Hmmh, $package doesn't work for me. I've searched the archive and have > seen that DH_COMPAT should be IMHO a environment variable inside the > rules file (e.g. > http://lists.debian.org/debian-mentors/2001/04/msg00011.html). I have > defined it and set to 4 It _used to_ be the case that it was an environment variable set (and exported) by ./debian/rules, but then people realized that under this configuration, debhelper would behave differently when run by the makefile than it would when run manually (for testing, debugging, etc.). So debhelper was modified to look at ./debian/compat (with DH_COMPAT as an override). I guess you can still use export DH_COMPAT=4, which makes ./debian/ cleaner IMHO, but you have to remember to set that variable when manually running dh_* commands.. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: All files are in DESTDIR but non will be copied into the packages
Justin Pryzby wrote: It _used to_ be the case that it was an environment variable set (and exported) by ./debian/rules, but then people realized that under this configuration, debhelper would behave differently when run by the makefile than it would when run manually (for testing, debugging, etc.). So debhelper was modified to look at ./debian/compat (with DH_COMPAT as an override). I guess you can still use export DH_COMPAT=4, which makes ./debian/ cleaner IMHO, but you have to remember to set that variable when manually running dh_* commands.. Ok, now I understand. Many thanks for your qualified help! Cheers, Timo
Re: RFS: ksudoku -- sudoku puzzle generator/solver
On Friday 11 November 2005 03:45 am, Christoph Haas wrote: > - The orig.tar.gz differs from the upstream tarball. It's just a > rename of the directory inside and the admin/CVS directory is > removed. It's a religious issue but I would rather leave the original > upstream archive intact. The CVS wouldn't show up in the final > package anyway. Changed; lintian will complain now, though :- ) > - You patched ksudoku-0.3/doc/en/index.docbook. Would that be better > solved through dpatch? Upstream will be including an updated index.docbook in the next release (there is active development), so I didn't think it was necessary to break out the patch management systems just yet. > - The debian/copyright lacks the years of copyright. Fixed. > - A 'desktop' file would be nice in addition to the 'menu' file. > (Don't forget to call dh_desktop.) I'm not sure what you mean; a desktop file is installed as part of the upstream source, /usr/share/applnk/Games/ksudoku.desktop. I've added the call to dh_desktop, though I don't understand what it does -- the manpage is short and I have no application called update-desktop-database *shrug*. > - Some debhelper calls (like dh_link) are not needed. Removing dh_link will cause a lintian error about relative symlinks, actually... > - Could you send the manpages upstream so they can be included > in the orig.tar.gz at the next release? Yes, sent. > - The AUTHOR section of the man pages looks strange to me. Fixed. New version uploaded to my archive, no revision bump. Thanks for taking a look! -- Ryan Schultz "vi users are mammals, and they flip out and kill people *all the time.*" pgplPvAoCpTGk.pgp Description: PGP signature
RFS: orphaned package secpanel
I've packaged new upstream version of this orphaned package (and taged it's orphaning bug as ITA) source package at: http://www.ageda.net/debian/secpanel/ suggestions/sponsor welcome maybe it's not the most popular package in debian, but has some users... http://people.debian.org/~igloo/popcon-graphs/index.php?packages=secpanel thanks! -- Pedro Silva email: [EMAIL PROTECTED] Fingerprint = D92E 351B 988E E484 A287 0648 A9BC 5534 ADA0 4E9D signature.asc Description: Digital signature
Re: [gmail] Re: sponsor quake3 quake3-data packages
> > Do you know of any efforts to create DFSG q3a content, which would allow > > migration into main? (just curious) > > There is, but it's in very early stage: > http://www.planetgargoyle.com/openarena/ emphasis on *very* :) If it matures, I'll add it as an alternative, next to installation of the CD and the demo. -- greetz, marc I'm only judging on my experience with you, but I've never seen such a deficient species. Pilot - Crackers Don't Matter scorpius.homelinux.org 2.6.13.2 #1 Fri Sep 23 07:23:21 CEST 2005 GNU/Linux signature.asc Description: Digital signature
Debian Packaging Guide/Tutorial
I've been playing around with packaging up some of my projects for debian. I have gotten it to work, but I'm still having problems understanding some of the features that are available (for instance it took me forever to learn about the .config file). Is there any kind of tutorial or guide that explains all of the debian packaging system, which files do what, how to make upgrades go smoothly wihtout always removing then installing the package? Any kind of help would be appreciated thanks. -- o)Derek Wueppelmann (o (D .[EMAIL PROTECTED]D). ((` http://monkey.homeip.net/ ( ) ` signature.asc Description: This is a digitally signed message part
Re: Debian Packaging Guide/Tutorial
On Fri, Nov 11, 2005 at 02:25:18PM -0500, Derek The Monkey Wueppelmann wrote: > I've been playing around with packaging up some of my projects for > debian. I have gotten it to work, but I'm still having problems > understanding some of the features that are available (for instance it > took me forever to learn about the .config file). > > Is there any kind of tutorial or guide that explains all of the debian > packaging system, which files do what, how to make upgrades go smoothly > wihtout always removing then installing the package? Any kind of help > would be appreciated thanks. http://www.debian.org/devel/ has lots of stuff for reading. Including the policy and the maintainer guide. Cheers, Michael -- Escape the Java Trap with GNU Classpath! http://www.gnu.org/philosophy/java-trap.html Join the community at http://planet.classpath.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: ksudoku -- sudoku puzzle generator/solver
On Friday 11 November 2005 18:55, Ryan Schultz wrote: > On Friday 11 November 2005 03:45 am, Christoph Haas wrote: > > - The orig.tar.gz differs from the upstream tarball. It's just a > > rename of the directory inside and the admin/CVS directory is > > removed. It's a religious issue but I would rather leave the > > original upstream archive intact. The CVS wouldn't show up in the > > final package anyway. > > Changed; lintian will complain now, though :- ) That may be ugly but I think changing the upstream tarball is even worse. Perhaps you can convince the upstream to remove the CVS from the release tarballs. It really doesn't belong there. > > - You patched ksudoku-0.3/doc/en/index.docbook. Would that be better > > solved through dpatch? > > Upstream will be including an updated index.docbook in the next release > (there is active development), so I didn't think it was necessary to > break out the patch management systems just yet. Agreed. > > - A 'desktop' file would be nice in addition to the 'menu' file. > > (Don't forget to call dh_desktop.) > > I'm not sure what you mean; a desktop file is installed as part of the > upstream source, /usr/share/applnk/Games/ksudoku.desktop. I've added the > call to dh_desktop, though I don't understand what it does -- the > manpage is short and I have no application called > update-desktop-database *shrug*. My bad. Indeed there is a ksudoku.desktop file which is installed. IMHO in the wrong place though. It should be located in /usr/share/applications instead. (Although I admit I don't know where that's properly documented in the policy. Perhaps someone else has a pointer.) dh_desktop calls the update-desktop-database command from the desktop-file-utils package (if installed) through the maintainer scripts of your package. It's use is to tell e.g. KDE that the menu structure has changed and the *.desktop files have to be reloaded. Otherwise KDE wouldn't show a menu item of your newly installed package unless you relogin. > > - Some debhelper calls (like dh_link) are not needed. > > Removing dh_link will cause a lintian error about relative symlinks, > actually... Hmm. Appears like the "make install" creates a symlink with an absolute path: ln -s /usr/share/doc/kde/HTML/en/common \ /home/haas/.../ksudoku-0.3/debian/ksudoku/usr/share/doc/HTML/en/ksudoku/common And dh_link fixes absolute symlinks to relative symlinks when needed: ./usr/share/doc/kde/HTML/en/ksudoku/common -> ../common So dh_link is indeed important here. Leave it there. Let's fix the desktop issue (or prove me wrong once again) and I'll happily upload it. :) Christoph -- ~ ~ ".signature" [Modified] 1 line --100%--1,48 All -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian Packaging Guide/Tutorial
On Fri, Nov 11, 2005 at 02:25:18PM -0500, Derek The Monkey Wueppelmann wrote: > I've been playing around with packaging up some of my projects for > debian. I have gotten it to work, but I'm still having problems > understanding some of the features that are available (for instance it > took me forever to learn about the .config file). > > Is there any kind of tutorial or guide that explains all of the debian > packaging system, Not really, I don't think, since there isn't a single cannonical packaging system. Policy dicates some things, like that control and copyright must exist, and that rules must be a makefile. Other than that, you are on your own. You can pick and choose what tools you use (and thats supposed to be a good thing!). > which files do what, Probably best to read the dh_* manpages for this, as debhelper is the typical (?) packaging system. > how to make upgrades go smoothly wihtout always removing then > installing the package? Well, much of this is package specific. What exactly is the problem? A sufficiently generalized piece of documentation would be great, though. Suggestions for content: conffile handling (dpkg.org), maintscripts (debian women? I don't fully grok these yet!), and upgrade handling with eg. split packages and Replaces. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian Packaging Guide/Tutorial
On Fri, 2005-11-11 at 14:39 -0500, Justin Pryzby wrote: > A sufficiently generalized piece of documentation would be great, > though. Suggestions for content: conffile handling (dpkg.org), > maintscripts (debian women? I don't fully grok these yet!), and > upgrade handling with eg. split packages and Replaces. I've looked through most of these resources. However some of the packaging structure still seems to be missing. I know I mentioned this before but apparently if you have a config file in your debian directory this script is called prior to the preinst script and is supposed to be used for your debconf questions. What is interesting is that I haven't seen this any of this documented anywhere, I only happened upon it because a debian developer pointed it out. Is there any kind of documentation that would point out features like this out there. I'm not even terribly concerned with it all being in one location, I can do the collection of it myself. I just find that it makes it really hard to start building packages in an efficient manner when after several months of hacking away someone comes by and says "You know you should really be doing it this way" having no clue that that way even exsited. Sorry for the rant, it's just a little frustrating. -- o)Derek Wueppelmann (o (D .[EMAIL PROTECTED]D). ((` http://monkey.homeip.net/ ( ) ` signature.asc Description: This is a digitally signed message part
Re: Debian Packaging Guide/Tutorial
On Fri, Nov 11, 2005 at 04:02:56PM -0500, Derek The Monkey Wueppelmann wrote: > On Fri, 2005-11-11 at 14:39 -0500, Justin Pryzby wrote: > > > A sufficiently generalized piece of documentation would be great, > > though. Suggestions for content: conffile handling (dpkg.org), > > maintscripts (debian women? I don't fully grok these yet!), and > > upgrade handling with eg. split packages and Replaces. > > I've looked through most of these resources. However some of the > packaging structure still seems to be missing. I know I mentioned this > before but apparently if you have a config file in your debian directory > this script is called prior to the preinst script and is supposed to be > used for your debconf questions. What is interesting is that I haven't > seen this any of this documented anywhere, I only happened upon it > because a debian developer pointed it out. > > Is there any kind of documentation that would point out features like > this out there. I'm not even terribly concerned with it all being in one > location, I can do the collection of it myself. I just find that it > makes it really hard to start building packages in an efficient manner > when after several months of hacking away someone comes by and says "You > know you should really be doing it this way" having no clue that that > way even exsited. > > Sorry for the rant, it's just a little frustrating. Probably you think "man debconf-devel" is useful. Cheers, Michael -- Escape the Java Trap with GNU Classpath! http://www.gnu.org/philosophy/java-trap.html Join the community at http://planet.classpath.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian Packaging Guide/Tutorial
On Fri, Nov 11, 2005 at 04:02:56PM -0500, Derek The Monkey Wueppelmann wrote: > On Fri, 2005-11-11 at 14:39 -0500, Justin Pryzby wrote: > > > A sufficiently generalized piece of documentation would be great, > > though. Suggestions for content: conffile handling (dpkg.org), > > maintscripts (debian women? I don't fully grok these yet!), and > > upgrade handling with eg. split packages and Replaces. > > I've looked through most of these resources. However some of the > packaging structure still seems to be missing. I know I mentioned this > before but apparently if you have a config file in your debian directory > this script is called prior to the preinst script and is supposed to be > used for your debconf questions. What is interesting is that I haven't > seen this any of this documented anywhere, I only happened upon it > because a debian developer pointed it out. In the specific case of debconf, I'll bet that the critical piece of missing information is debconf-devel.7 from package debconf-doc. > Sorry for the rant, it's just a little frustrating. File a bug against developers-reference (or whatever you feel the relevent document is), and I'll bet that it'll get fixed. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: ksudoku -- sudoku puzzle generator/solver
On Friday 11 November 2005 02:30 pm, Christoph Haas wrote: > My bad. Indeed there is a ksudoku.desktop file which is installed. IMHO in > the wrong place though. It should be located in /usr/share/applications > instead. (Although I admit I don't know where that's properly documented > in the policy. Perhaps someone else has a pointer.) I found a message[1] on debian-kde mentioning this; seems to be an XDG file location thing. I've moved it; however, it seems like kdevelop, KDE's IDE, defaults to installing there, so who knows? > dh_desktop calls the update-desktop-database command from the > desktop-file-utils package (if installed) through the maintainer scripts > of your package. It's use is to tell e.g. KDE that the menu structure has > changed and the *.desktop files have to be reloaded. Otherwise KDE > wouldn't show a menu item of your newly installed package unless you > relogin. I've found that KDE actually seems to have some magic to do this without being told (like with 'make install'), but I don't think GNOME will. Thanks for explaining. New version uploaded. Thanks again! [1] http://lists.debian.org/debian-kde/2004/02/msg00132.html -- Ryan Schultz "vi users are mammals, and they flip out and kill people *all the time.*" pgpC4po72t19u.pgp Description: PGP signature
Re: Debian Packaging Guide/Tutorial
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/11/2005 07:02 PM, Derek "The Monkey" Wueppelmann wrote: > On Fri, 2005-11-11 at 14:39 -0500, Justin Pryzby wrote: > > >>A sufficiently generalized piece of documentation would be great, >>though. Suggestions for content: conffile handling (dpkg.org), >>maintscripts (debian women? I don't fully grok these yet!), and >>upgrade handling with eg. split packages and Replaces. > > > I've looked through most of these resources. However some of the > packaging structure still seems to be missing. I know I mentioned this > before but apparently if you have a config file in your debian directory > this script is called prior to the preinst script and is supposed to be > used for your debconf questions. What is interesting is that I haven't > seen this any of this documented anywhere, I only happened upon it > because a debian developer pointed it out. > > Is there any kind of documentation that would point out features like > this out there. I'm not even terribly concerned with it all being in one > location, I can do the collection of it myself. I just find that it > makes it really hard to start building packages in an efficient manner > when after several months of hacking away someone comes by and says "You > know you should really be doing it this way" having no clue that that > way even exsited. > > Sorry for the rant, it's just a little frustrating. Maybe Debian Women [1]Wiki Articles about Packaging and Building could be of your interest, and also the [2]Involvement webpage. [1]http://women.alioth.debian.org/wiki/index.php/English/HomePage [2]http://women.alioth.debian.org/involvement/ Kind regards, - -- Felipe Augusto van de Wiel (faw) "Debian. Freedom to code. Code to freedom!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Debian - http://enigmail.mozdev.org iD8DBQFDdWTuCjAO0JDlykYRAlqIAKCQ9URzuZ8n8vArMO9JrVcMBT7m3gCfS4AG Jr/7L0gSI+ZL0dSaCLVPp4U= =0bMI -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
