Ubuntu – Find projects that use a particular programming language in Launchpad

developmentlaunchpadsearchvala

On Launchpad.net, most projects list the programming language(s) their software uses:

alt text

It would be useful if there was a way to get a list of all the projects that use "X" programming language, in my case Vala. Does Launchpad provide this functionality? Are there any 3rd party tools that can do this?

Best Answer

As Marco Ceppi has pointed me towards launchpadlib, I wrote a little script that will do this for you. download it here

Run the script by calling python name_of_the_script.py in a Terminal after you've downloaded and saved it. It will ask you for a programming language, case insensitive, and a search query (where wildcards, *, are allowed). If you leave either of them blank, it will search across all, rather than none.

You'll need to install python-launchpadlib before you can use it.

Here's some example output:

stefano@3000-G530:~$ python test.py 
Enter a programming language or leave blank to find projects in all languages:
>>> Python
Enter a search query or leave blank for all:
>>> Calculator
calcool - A document based calculator tool...
evias - Web site used to apply Eve DB dump to Eve API results and get th...
txevolver - txEvolver is a Twisted-based set of libraries for performing ...
[...]

Related Solutions

Ubuntu – How to figure out the add-apt-repository command by looking at a launchpad project

PPAs in Launchpad are connected to People/Teams, rather than projects. Your best bet is to click on the "Maintainer" for the project ("Cardapio Team" in this case):

From there, follow the link on under "Personal Package Archives" on their profile page. There may be multiple options here, you'll just have to use your best guess based on their names.

The name of the PPA will be on this page:

However, this is not guaranteed to work, as the developers can use any PPA they want for their project. It could be ppa:someunrelatedteam/foobar for all you know. There is no way to know for sure from the Launchpad project.

Alternatively, googling "[project name] PPA" tends to give good results.

PPA – How to Create a PPA for a Working Program

That's a very wide question. I'll try to answer as much as I can, but it definitely WON'T be a step-by-step instruction. This is because there is no step-by-step algorithm for creating a package. The way you'll do it depends on many factors, mostly on the type of package (application, library), the structure of source, and many details.

Luckily, there is a thorough guide at http://packaging.ubuntu.com

I'll try to help you a bit with understanding the whole process, so when you'll be a bit more familiar with it. The Packaging Guide includes resources for additional help.

First of all you should realize that creating a package (a .deb file) is a separate process from creating a PPA. Creating a PPA is a matter of going to your Launchpad's profile and clicking "Create a new PPA" link. That's all. It's created, it works, but it's empty. To upload a package you must first create one. But let me first answer some of your minor questions.

The programing language DOES NOT matter at all. It can be a C++ application, Bash script, Brainfuck Hello World, a single README file, or a set of cool photos. Packages may contain any file. During installation the package gets extracted to the root ("/") of your filesystem. This way they can put some files in the binaries folder, add some wallpapers to the GNOME default set, or provide user with a Bash script.
You DO need to add something to the source. It must be a top-level directory named "debian". There will be some files with the package details - they will be used to define what type the package is, etc.
Dependencies are listed in one of this files (amongst other details). Where to get them from? They are simply other packages that your application uses. The developer of the application WILL know what libraries and resources his program requires, so he shouldn't have much trouble with listing them.
- Some tools used to build a package (pbuilder) can fill in the dependencies automatically, probably by determining what your app requires during compilation.
It is also highly recommended to use AutoTools. That's other thing you may need to add, but probably almost every piece of software uses them already. AutoTools is a set of extremely helpful programs - automake, autoconf and autoscan to name a few. When you compile&install a program with the famous ./configure && make && make install then the autotools are used to automatically deal with the source, to prepare other resources included with the source to installation, and to extract the result of the compilation to appropriate place (to answer your question: The build will extract to MANY separate places. The binaries will go to /usr/local/bin, the docs to /usr/local/share/docs etc. Moreover, a binaries from a package will go to even different places, f.e. the binaries to /usr/bin. How to deal with this complicated directories layout? Use AutoTools - it will care about it automatically, and that's why they are so useful).

Building a .deb package may look as a really complicated process, but it's not that difficult. I highly recommend you the official Ubuntu guide to creating packages: http://packaging.ubuntu.com

It's HUGE, but you'll see you can probably skip most parts of that text (depending on what package you are going to build). Basically, packaging process consists of these parts (all are clearly explained in The Guide):

Init some tools used to build packages.
Get the source
Create the ./debian directory and fill it with required data
Build the package with debuild [That should create a set of files, including *.dsc, *_source.build, *_source.changes, which are responsible for the data about the package, and how to deal with it (you will also have a source .tar.gz)]
Test whether everything works by running pbuilder locally (it will take all these files mentioned above and try to combine them into a .deb package, by automatically building the source with the help of AutoTools - that's why they are crucial for packaging [frankly speaking - not - you can get along without them or with some alternatives, but that's the very easiest approach, and other may require some advanced setup, as you'll need to instruct the builder how to build the source (using ./debian/rules file) - but that's not for beginners]) - if you just want to get a .deb package, it's done.

Now you'll have to upload it to your PPA, which is explained on this help page: https://help.launchpad.net/Packaging/PPA/Uploading

Use dput to upload these files to Launchpad
Launchpad will run pbuilder on their computers, and generate packages in a clean environment
Finally, the packages should appear in the PPA.

As you see creating a PPA is not that straightforward. But don't be frightened, it's also not that difficult. Moreover, I recommend you not to encourage developers to use a PPA, as probably they won't listen to you, since they would need to do some additional job (and if they wanted to they would have done it already), but you may want to try to support Ubuntu developers and the whole community and provide them with packages you've prepared :)

I wish you good luck with creating packages, hope you'll find my answer helpful :)

Your friend, Rafał Cieślak

Best Answer

Related Solutions

Ubuntu – How to figure out the add-apt-repository command by looking at a launchpad project

PPA – How to Create a PPA for a Working Program

Related Question