Hi,
the build service is supporting the storage of pattern files from now on. Additionally it does create .ymp files for each repo from it.
.ymp files (read One-Click install files) are very usefull to make it easy for your users to install a set of packages.
We will also highlight ymp files in the new End-User interface comming to software.opensuse.org next week. This means, if a ymp file does match the user search request, it will be shown on top of the search list. Any other matches will come afterwards.
There is no need to create patterns just for one package, because the new End-User interface will create them on the fly when a user clicks on a package to install.
So, if you want to create also pattern files for your project, have a look here:
http://en.opensuse.org/Build_Service_Tutorial#Create_Patterns
Example pattern files can be also found in the KDE:KDE4 project, the resulting ymp files are here for example:
http://download.opensuse.org/repositories/KDE:/KDE4/SUSE_Factory/
The api is validating your files on uploading, so have a deeper look on the output, if you get an error on uploading. But it is really easy to create patterns based on the example files.
happy to help you in case of trouble :) adrian
Adrian Schröter wrote:
Hi,
the build service is supporting the storage of pattern files from now on. Additionally it does create .ymp files for each repo from it.
Hi,
is it possible to have patterns that span multiple projects? Eg:
* latest PHP (packages from server:php/$distro) * latest PHP + MySQL combo (server:php/server_database_$distro + server:database/$distro) * latest PHP + Apache combo (server:php/server_apache_$distro + Apache/$distro) * latest LAMP combo (not yet?)
Users sometimes won't get these inter-project dependencies right and they try to install latest apache + php built against stock apache or something similar. There's an exponential number of ways to mess it up ;), so I think such patters would really rock here (if supported).
Michal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tuesday 31 July 2007 17:08:44 wrote Michal Marek:
Adrian Schröter wrote:
Hi,
the build service is supporting the storage of pattern files from now on. Additionally it does create .ymp files for each repo from it.
Hi,
is it possible to have patterns that span multiple projects? Eg:
- latest PHP (packages from server:php/$distro)
- latest PHP + MySQL combo (server:php/server_database_$distro + server:database/$distro)
- latest PHP + Apache combo (server:php/server_apache_$distro + Apache/$distro)
- latest LAMP combo (not yet?)
Yes, you need to have or create a project which builds against all the other needed projects. The build service adds all used repositories automatically to the created ymp file.
Users sometimes won't get these inter-project dependencies right and they try to install latest apache + php built against stock apache or something similar. There's an exponential number of ways to mess it up ;), so I think such patters would really rock here (if supported).
right, so we do support exactly this :)
bye adrian
On Tuesday 31 July 2007 18:33:43 wrote Adrian Schröter:
On Tuesday 31 July 2007 17:08:44 wrote Michal Marek:
Adrian Schröter wrote:
Hi,
the build service is supporting the storage of pattern files from now on. Additionally it does create .ymp files for each repo from it.
Hi,
is it possible to have patterns that span multiple projects? Eg:
- latest PHP (packages from server:php/$distro)
- latest PHP + MySQL combo (server:php/server_database_$distro + server:database/$distro)
- latest PHP + Apache combo (server:php/server_apache_$distro + Apache/$distro)
- latest LAMP combo (not yet?)
Yes, you need to have or create a project which builds against all the other needed projects. The build service adds all used repositories automatically to the created ymp file.
btw, there even needs not to be any package inside, you can just create a project which reuses all the others and add your pattern(s) to it ...
bye adrian
On 7/31/07, Adrian Schröter adrian@suse.de wrote:
Hi,
the build service is supporting the storage of pattern files from now on. Additionally it does create .ymp files for each repo from it.
.ymp files (read One-Click install files) are very usefull to make it easy for your users to install a set of packages.
Hi
I tried creating a ymp, it can be found here: http://download.opensuse.org/repositories/home:/cyberorg/SUSE_Factory/
Trying to test it I get following errors:
prime:~ # /sbin/YaST2 MetaPackageUrlHandler http://download.opensuse.org/repositories/home:/cyberorg/SUSE_Factory/compiz... File does not exist: 400 URL missing at /usr/share/YaST2/modules/MetaPackageParser.pm line 27 Can't undef active subroutine during global destruction.
prime:~ # /sbin/YaST2 MetaPackageUrlHandler http://download.opensuse.org/repositories/KDE:/KDE4/SUSE_Factory/KDE4-BASIS.... File does not exist: 400 URL missing at /usr/share/YaST2/modules/MetaPackageParser.pm line 27 Can't undef active subroutine during global destruction.
prime:/home/cyberorg/Desktop # /sbin/YaST2 MetaPackageUrlHandler ./compiz-git-all.ymp File does not exist: 400 URL must be absolute at /usr/share/YaST2/modules/MetaPackageParser.pm line 27 Can't undef active subroutine during global destruction.
using Alpha6+ and yast2-metapackage-handler-0.4-4
Any other way to test?
-J --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wednesday 01 August 2007 13:28:52 wrote CyberOrg: ...
Trying to test it I get following errors:
prime:~ # /sbin/YaST2 MetaPackageUrlHandler http://download.opensuse.org/repositories/home:/cyberorg/SUSE_Factory/compi
z-git-all.ymp File does not exist: 400 URL missing
at /usr/share/YaST2/modules/MetaPackageParser.pm line 27 Can't undef active subroutine during global destruction.
hm, the module in Factory seems to be broken atm :/
I just tested it on 10.2 with backported yast metapackage-handler and that works ...
Feel free to make a bugreport for it, I will create one otherwise when I test the 0.5 version of it next week ...
bye adrian
On 8/1/07, Adrian Schröter adrian@suse.de wrote:
On Wednesday 01 August 2007 13:28:52 wrote CyberOrg: ...
Trying to test it I get following errors:
prime:~ # /sbin/YaST2 MetaPackageUrlHandler http://download.opensuse.org/repositories/home:/cyberorg/SUSE_Factory/compi
z-git-all.ymp File does not exist: 400 URL missing
at /usr/share/YaST2/modules/MetaPackageParser.pm line 27 Can't undef active subroutine during global destruction.
hm, the module in Factory seems to be broken atm :/
Sorry, false alarm, mvidner corrected me, it was a user error :)
I should hae used:
/sbin/yast2 MetaPackageHandler http://download.opensuse.org/repositories/home:/cyberorg/SUSE_Factory/compiz...
which works.
Cheers
-J --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
buildservice@lists.opensuse.org
-
Adrian Schröter -
CyberOrg -
Michal Marek