Linking packages from released distributions
Hello, I wanted to create a modified courier-authlib package (to be exact: with added mysql backend, requires just a specfile patch AFAIK) for 10.1, but wasn't able to link to the package. Michael Schröder told me that the sources for 10.1 were not uploaded - I think this should be changed ;-) The reasons why I do not want to link to the Factory package are the same with for YOU updates - I want to minimize the changes I need to do to the whole system (so: no version upgrades) and would like to have an automated package rebuild in case there's a security update for courier-authlib. Of course, I can upload the 10.1 sources myself - but I don't consider this a very good idea... BTW: Can I upload a src.rpm instead of a tarball also? Regards, Christian Boltz PS: Maybe wildcard linking would be an interesting feature ("link to package foobar from the distributions I'm building packages for") - but in this case you would need the option to apply a patch to a limited set of your build targets. The alternative is to create a project per target distribution and to apply the patch to the distributions that need it. -- wie jeder weiß ist Debian auf ISDN die langsamste bekannte Methode Selbstmord zu begehen ("Selbstmord durch Erosion") [http://blog.koehntopp.de/archives/113-Debian-ist-doch-schlecht..html]
Am Thursday 25 May 2006 15:31 schrieb Christian Boltz:
Hello,
I wanted to create a modified courier-authlib package (to be exact: with added mysql backend, requires just a specfile patch AFAIK) for 10.1, but wasn't able to link to the package.
Michael Schröder told me that the sources for 10.1 were not uploaded - I think this should be changed ;-)
The reasons why I do not want to link to the Factory package are the same with for YOU updates - I want to minimize the changes I need to do to the whole system (so: no version upgrades) and would like to have an automated package rebuild in case there's a security update for courier-authlib.
Of course, I can upload the 10.1 sources myself - but I don't consider this a very good idea...
We do plan to host the source in future as well, but after we do really maintain the distribution itself inside of the build service. You will be able to link against a released/old source version than from the source repository.
BTW: Can I upload a src.rpm instead of a tarball also?
no, because not all tools will be able to handle a src.rpm. And you will not be able to build non rpm packages from it. But someone could patch the commandline tool osc to import a src.rpm by extracting it (hint hint ;)
PS: Maybe wildcard linking would be an interesting feature ("link to package foobar from the distributions I'm building packages for") - but in this case you would need the option to apply a patch to a limited set of your build targets. The alternative is to create a project per target distribution and to apply the patch to the distributions that need it.
hm, indeed an interessting idea. -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de
Hello, Am Donnerstag, 25. Mai 2006 16:13 schrieb Adrian Schröter:
Am Thursday 25 May 2006 15:31 schrieb Christian Boltz:
I wanted to create a modified courier-authlib package [...] for 10.1, but wasn't able to link to the package.
Michael Schröder told me that the sources for 10.1 were not uploaded - I think this should be changed ;-) [...] We do plan to host the source in future as well, but after we do really maintain the distribution itself inside of the build service.
You will be able to link against a released/old source version than from the source repository.
I'm glad to hear this. Do you already have any timeframe when this will happen? Regards, Christian Boltz -- - Macs sind für die, die nicht wissen wollen, warum Ihr Rechner funzt. - Linux ist für die, die wissen wollen, warum er funzt. - DOS ist für die, die wissen wollen, warum er nicht funzt, und - Windows ist für die, die nicht wissen wollen, warum er nicht funzt.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Christian Boltz wrote:
I wanted to create a modified courier-authlib package (to be exact: with added mysql backend, requires just a specfile patch AFAIK) for 10.1, but wasn't able to link to the package.
Michael Schröder told me that the sources for 10.1 were not uploaded - I think this should be changed ;-)
Sources ? you mean spec files ?
The reasons why I do not want to link to the Factory package are the same with for YOU updates - I want to minimize the changes I need to do to the whole system (so: no version upgrades) and would like to have an automated package rebuild in case there's a security update for courier-authlib.
Yes but you could link to the Factory package and define build targets as of 10.1, 10.0, ... or not ?
Of course, I can upload the 10.1 sources myself - but I don't consider this a very good idea...
No, pristine sources must be referred to by fully qualified URLs and downloaded by the build process. I don't know how this is currently handled by BS.
BTW: Can I upload a src.rpm instead of a tarball also?
Why would you want to do that ? I don't think that would be a good idea, pristine sources must be guaranteed.
PS: Maybe wildcard linking would be an interesting feature ("link to package foobar from the distributions I'm building packages for") - but in this case you would need the option to apply a patch to a limited set of your build targets. The alternative is to create a project per target distribution and to apply the patch to the distributions that need it.
No, the pattern for that is to use macros, e.g.
%if %suse_version >= 1000
...
%endif
I'd strongly recommend to use a single spec file all builds, makes life
so much easier (when you apply a change, patch, new version/release,
it's a single spec file to manage).
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\
Hello, Am Donnerstag, 25. Mai 2006 16:14 schrieb Pascal Bleser:
Christian Boltz wrote:
Michael Schröder told me that the sources for 10.1 were not uploaded - I think this should be changed ;-)
Sources ? you mean spec files ?
Not only - I mean the complete content of the src.rpms (tarballs, patches, and specfiles, yes). In short: everything you need to rebuild a package ;-)
The reasons why I do not want to link to the Factory package are the same with for YOU updates - I want to minimize the changes I need to do to the whole system (so: no version upgrades) and would like to have an automated package rebuild in case there's a security update for courier-authlib.
Yes but you could link to the Factory package and define build targets as of 10.1, 10.0, ... or not ?
Yes, I could - but I'd like to stick with the version that comes with the distribution and just add the necessary patch. As I already said, call it the YOU-approach...
Of course, I can upload the 10.1 sources myself - but I don't consider this a very good idea...
No, pristine sources must be referred to by fully qualified URLs and downloaded by the build process. I don't know how this is currently handled by BS.
You have a choise to enter a filename (probably works with URLs also, I didn't test that yet) or to upload a file. But this wasn't my point - I think it's pointless that I have to upload the sources of SUSE core packages myself.
BTW: Can I upload a src.rpm instead of a tarball also?
Why would you want to do that ?
It's easier than separate uploading of the tarball, patches and the spec file ;-)
PS: Maybe wildcard linking would be an interesting feature ("link to package foobar from the distributions I'm building packages for") - but in this case you would need the option to apply a patch to a limited set of your build targets. The alternative is to create a project per target distribution and to apply the patch to the distributions that need it.
No, the pattern for that is to use macros, e.g. %if %suse_version >= 1000 ... %endif
I'd strongly recommend to use a single spec file all builds, makes life so much easier (when you apply a change, patch, new version/release, it's a single spec file to manage).
Sounds correct. Since I'm really new to packaging [1], I'm not familar with these details yet ;-) Regards, Christian Boltz [1] the Fontlinge package [2] is the first RPM I ever built, and the specfile was mostly done by David Haller ;-) [2] BTW: Even if it has version 2.1, it isn't the final 2.1 (which wasn't released yet). -- Aber bei Sendmail weiss man ja nie, ist ja ne Mischung aus Programmier- sprache und halben Betriebssystem, die bei geeigneter Konfiguration wie ein MTA aussehen kann... [Steffen Dettmer in suse-linux]
participants (3)
-
Adrian Schröter
-
Christian Boltz
-
Pascal Bleser