Closed ZyX-I closed 9 years ago
It appears that I forgot Manifest update.
And you have mistake in SRC_URI.
Done. Thanks for the SRC_URI
fix, as well. (Which is fairly embarrassing; I know I tested both release ebuilds. Bah!)
@leycec You must run tests with empty directory pointed by DISTDIR (or at least with directory pointed by DISTDIR that does not contain sources for ebuilds you are testing). Otherwise ebuild
will simply use already downloaded sources. It also appears that ebuild is not going to regenerate data for files that are already in the manifest.
So if “testing” is ebuild … fetch
(or anything else that includes fetch stage) then you need to remove files from DISTDIR (or provide a clean directory). If “testing” is ebuild … manifest
(which is what I usually do, though making sure that ebuild did download something) you must both remove existing Manifest and existing files.
You must run tests with empty directory pointed by DISTDIR (or at least with directory pointed by DISTDIR that does not contain sources for ebuilds you are testing).
Clever. I'll have to remember that. You're just a bundle of useful Portage tips. :grin:
Otherwise ebuild will simply use already downloaded sources. It also appears that ebuild is not going to regenerate data for files that are already in the manifest.
Right. I realized that about 5 picoseconds after my prior reply. /sigh
So if “testing” is ebuild … fetch (or anything else that includes fetch stage) then you need to remove files from DISTDIR (or provide a clean directory). If “testing” is ebuild … manifest (which is what I usually do, though making sure that ebuild did download something) you must both remove existing Manifest and existing files.
It's unfortunate that ebuild
doesn't provide a command for automatically cleaning source files for the passed ebuilds from ${DISTDIR}
– say, cleandist
. Since it doesn't, I suppose I'll probably automate this unctuous task with shell script.
Thanks, ZyX.
Add ebuilds for new powerline version
Created automatically by release script