|
Bugzilla – Full Text Bug Listing |
| Summary: | license.zip and info.txt in media.1/ | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Duncan Mac-Vicar <dmacvicar> |
| Component: | YaST2 | Assignee: | Duncan Mac-Vicar <dmacvicar> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | aj, coolo, jsuchome, locilka, ro |
| Version: | Alpha 7 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | 300982 | ||
| Bug Blocks: | |||
|
Description
Duncan Mac-Vicar
2007-08-01 15:16:25 UTC
Uff, this licensing stuff is a closed book for me :( Lukas, please check Product layout is designed and maintained by product/project managers. Additionally, Add-On-Creator should be changed according such layout changes. What needs to be done here? Currently, we put licenses.tar.gz (has been renamed!) into / -- this was, what was suggested by several folks in the discussion. Currently we have
* Installation (Base Product)
/license.tar.gz file in the root of the media and it should be protected by
SHA1 and checked by Linuxrc before installation starts. Linuxrc also copies
the file to inst-sys.
* Add-Ons
/license.tar.gz file protected by SHA1 downloaded by package bindings
(this case will probably need to check the SHA1)
If there are no product related data in media specific directory, then this can be closed. "this case will probably need to check the SHA1" I did a little extension on the content file together with snwint to be able to get more checksums in that file. now we have: META SHA1 $SUM $FILENAME (files based below $DESCRDIR) KEY SHA1 $SUM $FILENAME (gpg keys in / to import into rpmdb) and new: HASH SHA1 $SUM $FILENAME (files relative to / without a leading "/") added licenses.tar.gz to the list of files to be included in this last group. *** This bug has been marked as a duplicate of bug 300982 *** Oops, to quick. What about info.txt? What is info.txt for? info.txt in inst-sys is an identical copy of README.BETA
That file contains something like:
--- cut ---
This is Beta distribution of openSUSE 12.6
...
your
openSUSE Team
--- cut ---
But, is it a media property or a product property. What's the difference, Duncan? Coolo, can you help here, please? Not sure there is a clear definition. But I guess info.txt is just a media addon, not part of the product. As a matter of fact I think we never had a product with it. Only media for alphas or betas. But then again, it's very likely we put it on e.g. a cover mount medium to mark the medium as such. Then we can close this. |