Anyone can help me in translating my application (baires) to french?
It is very small job - 35 words & phrases for application and small html help.
2 files for translation are here: http://www.beli.ws/apps/baires/translate.tar.gz
Ladies and gentlemen,
I announce my 1st Qt4 application - Baires.
Baires is a program that helps you easily resize bunch of pictures from one directory and place it to the same or another, with just one click (after initial setup, of course).
I'm trying to build a package on Launchpad's Debian build system for PPAs but I'm having some issues with a certain package.
The package I'm trying to build (zorin-xwinwrap) contains a source C file which I'm trying to get to compile and build on Launchpad's server so that it would install and work on 32 bit (i386) and 64 bit (amd64) systems.
So I'm writing a small package manager, and a problem I've run into is making the symbolic links to files.
It installs the package to /usr/pkg/name-version, and then reads a file to determine what symbolic links to make.
Suppose I have an installer program or source tarball for some program I want to install. (There is no Debian package available.) First I want to create a .deb package out of it, in order to be able to cleanly remove the installed program in the future (see Uninstalling application built from source, If I build a package from source how can I uninstall or remove completely?).
Hello,
I am not sure if this is the right area to ask this question, so if it is not I am sorry. First off I am very new to Linux, and thought I would start out with openSuse.
I have 12.4, and I have a package that is a Recursive Package Manager (rpm). I need to install it. There is also a Fedora version of the package, but its the same thing. When extracting the package, I have no idea where it goes. I have also tyred the "Alien" program in the terminal, but it didn't really seem to work, unless the program extracts it into an unknown location.
I'm trying to roll a package of a small and relatively simple Qt program.
The source tree has the appropriately filled debian/ subdirectory, with control, rules, changelog and other nessesary metadata.
In particular, the debian/control file declares about the binary package:
Depends: ${shlibs:Depends}, ${misc:Depends}
-- so that runtime dependencies could be determined automatically.
Howeve
I'm making Ubuntu packages from source code of a geology program. I can make debs on my pc and also Launchpad is able to make binary packages for 32-bit OS.
I noticed an strange behavior of Launchpad. It makes both development (libfoo-dev) and shared library (libfoo) from uploaded source code for i386 though makes only binary package for amd64 from same code.