First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 116348
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Daniel Ahlberg (RETIRED) <aliz@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Alec Warner <antarus@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 116348 depends on: Show dependency tree
Show dependency graph
Bug 116348 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2005-12-21 20:53 0000
src_unpack() {
        unpack ${A} ; cd ${S}
        epatch ${FILESDIR}/${P}-setsid.patch

        ebegin "Trying to download the latest hddtemp.db file"
        wget -q --timeout=10 http://www.guzu.net/linux/hddtemp.db
        eend $?
}
wget should not be used in src_unpack.  That db file should be in SRC_URI
instead of in src_unpack, so that portage can fetch and digest it properly. 
This also defeats people who use emerge -f to fetch all important files, only
to fail here with no internet connection.

------- Comment #1 From SpanKY 2005-12-21 21:00:29 0000 -------
i dont really think this is an issue ... the .db file is constantly updated
upstream, the wget has a small timeout, and if it fails, there is a local (old)
cache to fall back on

------- Comment #2 From Alec Warner 2005-12-21 21:21:25 0000 -------
As Zac suggested on IRC, put the fetching in pkg_config and inform the user
that they have to run it after installation to fetch the newer db.

------- Comment #3 From Mark Loeser 2006-02-16 13:00:52 0000 -------
The pkg_config idea sounds best to me if this is a moving target.

Spock, any reason not to change it?

------- Comment #4 From Michal Januszewski 2006-02-19 07:56:55 0000 -------
The only reason for not changing it earlier was that I've forgotten about this
bug (since it wasn't assinged to me) :)

A fixed ebuild is now in CVS. I didn't want to make any changes in the old
ebuilds, so we'll have to wait for the new one to be marked stable so that
-beta13 can be removed from the tree.

First Last Prev Next    No search results available      Search page      Enter new bug