El Dissabte, 9 de maig de 2015, a les 09:23:26, Mechtilde va escriure:
> Hello
> 
> Am 05.05.2015 um 23:45 schrieb Mike Hommey:
> > On Sun, May 05, 2013 at 02:22:04PM +0200, Joerg Jaspert wrote:
> >> Hello world,
> >> 
> >> Now with wheezy happy and out the door, we should finally tackle a long
> >> open issue. Developer repositories (AKA PPA) for Debian.
> > 
> > Now with jessie happy and out the door, what is the status of Developer
> > repositories for Debian?
> 
> Why can't you use people.debian.org for this?
> 
It's not an option for a non developer member. :-(

I think that this topic seems not be a interesting and to me it's a very 
frustrating issue. Let me explain my case:

I'm a new maintainer and I'm working hard with another person to build a huge 
number of packages for robotics. But, this situation could be similar for 
other people.

If I'm not wrong, if someone wants to contribute packaging for Debian, more or 
less must:

a) take a upstream package that you want to work on
b) work on the package, copyrights, lintian clean, etc. It's better to work in 
a good environment, like pbuilder, or similar. 
c) test the package.
d) search for a sponsor, to upload the package for the revision of ftp-masters
e) maintain it (bugs, transitions, etc)

Before to arrive to point d), there are a lot of things to do. In my case I 
have had to create pbuilder environment (to work with), and a reprepro 
repository (to install easily in my boxes). It's not too much work, but it's 
time and for instance, I'm not able to test in "exotic" architectures or 
different ones than the typical x86.

mentors.d.o could help, but you must sent the binary and _only_ checks the 
package with lintian.

Because several reasons I try to avoid to work with any Ubuntu service. 
However, my partner convince me and prepare a ppa for our packages. And, it 
worked really well!!!!!

IMHO it's a wonderful tool to work with. When you thing that your package it's 
more or less ok, you sent with dput the sources to the launchpad and it builds 
your package and if all is ok, it publishes it automatically (for i386 and 
amd64). If you work with several packages, it takes the dependencies from your 
ppa (or other you have configured?). It saves a lot of time.

My first though was, ok, I can create a ppa for any Ubuntu version, maybe I 
could create for a Debian one, as Ubuntu derives from Debian it should be 
natural. But no [1], and IMHO there are not any interest to do that. Canonical 
help you, and promote you that build any Debian package for Ubuntu, but no the 
reversal order.

I know that some people have tried to make a similar service [2], but there's 
no publish option of the package and lacks several things.

So, I think that it could be very interesting for the project to have some 
kind of service, similar to ppa that:

1) let the people built his/her package in a Sid, stable-backport environment, 
or custom (stable+some addons)

2) Check the package built with lintian plus some licensecheck or whatever.

3) publish the package to be tested .

This service could be a complement to mentors or Alioth. Also, maybe it could 
help to ftp-masters/sponsors if you try to publish your package and pass all 
the checks or show some important information about it.

Of course it could have problems:

- depending of the numbers of architectures supported, and the number of 
users, you could have a saturated service.
- I don't know which legal problems the organization could have is someone 
upload to that service some software with some problematic license.
- other problems that I'm almost sure that people in this list will find ;-)

So, that's my opinion,
thanks for reading.

Leopold


[1] https://bugs.launchpad.net/launchpad/+bug/188564
[2] http://debomatic-amd64.debian.net/


-- 
--
Linux User 152692     GPG: 05F4A7A949A2D9AA
Catalonia
-------------------------------------
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to