|
Bugzilla – Full Text Bug Listing |
| Summary: | make ARCHIVES.gz a package and install it as pin dependency | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Kevin Ivory <Ivory> |
| Component: | Selections | Assignee: | Stefan Dirsch <sndirsch> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | andreas.hanke, suse-beta |
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Kevin Ivory
2005-09-13 07:28:25 UTC
Assigning to maintainer of pin. Martin, read the subject. :-) this is not that easy :-) integrating ARCHIVES.gz into a package is not really possible and it will kill another 10mb of space on the media. I will look into other ways to do that, checking the installation media (cd,dvd and also remote sources) to install it during the initial installation. It's far to late for 10.1, but i will look into that after 10.1 is final. Sorry for the delay. The idea sounds good :-) What about a dummy RPM with a post-install script? However, I see another problem: how to handle ARCHIVES.gz from multiple installation sources (OSS, non-free, maybe some external sources like packman)? (This problem also exists with the current implementation.) Suggestion: create a _directory_ /var/lib/pin/$suse_release and put the ARCHIVES.gz of all installation sources there (as ARCHIVES_$sourcename.gz). By default, pin should grep in /var/lib/pin/$suse_release/*, but maybe a parameter for $sourcename would be a good idea. Another idea: let the YaST2 "installation sources" module handle the ARCHIVES.gz (add a checkbox "download ARCHIVES.gz" for each installation source) and possibly save it below /var/adm/YaST/InstSrcManager/IS_CACHE_* instead of /var/lib/pin/. Sounds like a WONTFIX to me. |