Mailinglist Archive: yast-devel (47 mails)
| < Previous | Next > |
[yast-devel] YaST2 Team Meeting 2008-10-17
- From: Lukas Ocilka <lukas.ocilka@xxxxxxx>
- Date: Thu, 23 Oct 2008 10:31:57 +0200
- Message-id: <4900367D.6020003@xxxxxxx>
YaST2 Team Meeting 2008-10-17
=============================
Present: j(kupec|reidinger|srain|suchome|uhliarik),
l(ocilka|slezak), mzugec
Absent: kmachalkova, mvidner
Table of Contents
-----------------
1.) Licenses in Repositories (zypper)
2.) Add-On Creator
3.) Product Creator
4.) Package Bindings
1.) Licenses in Repositories (zypper)
-------------------------------------
zypper has to handle the stored product/repository licenses while adding
or using repositories. Accepting the license is required for a
repository to be used. An information about accepted license will be
stored to prevent from requiring to accept it over and over again.
2.) Add-On Creator
------------------
Products are still quite vaguely defined. Add-On creator needs a
definitive agreement on how the products are going to be created
(metadata, formats ...).
3.) Product Creator
-------------------
Product created without being signed automatically add insecure=1
Linuxrc parameter. Otherwise the product would be hardly usable because
of Linuxrc complaining all the time. This option will be well-described
in the Product Creator UI. See also http://en.opensuse.org/Linuxrc
(option Insecure).
4.) Package Bindings
--------------------
PB will offer functions to download and check signed repository files
via libzypp. The function is: Pkg::SourceProvideSignedFile (integer
repoid, integer medium, string filename, boolean optional) (bnc#409927).
--
Lukas Ocilka, YaST Developer (xn--luk-gla45d)
-----------------------------------------------------------------
Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.
=============================
Present: j(kupec|reidinger|srain|suchome|uhliarik),
l(ocilka|slezak), mzugec
Absent: kmachalkova, mvidner
Table of Contents
-----------------
1.) Licenses in Repositories (zypper)
2.) Add-On Creator
3.) Product Creator
4.) Package Bindings
1.) Licenses in Repositories (zypper)
-------------------------------------
zypper has to handle the stored product/repository licenses while adding
or using repositories. Accepting the license is required for a
repository to be used. An information about accepted license will be
stored to prevent from requiring to accept it over and over again.
2.) Add-On Creator
------------------
Products are still quite vaguely defined. Add-On creator needs a
definitive agreement on how the products are going to be created
(metadata, formats ...).
3.) Product Creator
-------------------
Product created without being signed automatically add insecure=1
Linuxrc parameter. Otherwise the product would be hardly usable because
of Linuxrc complaining all the time. This option will be well-described
in the Product Creator UI. See also http://en.opensuse.org/Linuxrc
(option Insecure).
4.) Package Bindings
--------------------
PB will offer functions to download and check signed repository files
via libzypp. The function is: Pkg::SourceProvideSignedFile (integer
repoid, integer medium, string filename, boolean optional) (bnc#409927).
--
Lukas Ocilka, YaST Developer (xn--luk-gla45d)
-----------------------------------------------------------------
Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.
| < Previous | Next > |