On Thu, 8 Sep 2005 16:03:58 -0700 Mark Knecht wrote: > On 9/8/05, Neil Bothwick <[EMAIL PROTECTED]> wrote:
> > > > ebuild /path/to/ebuild digest > > > > Always do this after modifying an ebuild. > > > > Neil, > Is there no difference when the ebuild is personal and held in > /usr/local/portage as opposed to one held by portage proper? no it still needs a manifest and digest files. see below for the quickest way to generate them. > > Also, is it important to ensure absolutely no overlap in names? > Since I just copied the one one in portage but didn't rename it I > wasn't sure I wouldn't do some damage to the database somehow. overlay will beat portage when emerge is figuring out which one to install. so if the ebuild files are identically named the one in overlay will be built. Not sure what happens if you have more than one overlay. By the way: emerge --digest jack-audio-connection will build the new digest thing, you no longer need to ebuild /long/path/balh.ebuild digest first. You will make sure you submit your changes to the ebuild to bugs.g.o won't you? Also remember someone made this ebuild -amd64 for a reason, it may not work (or worse it may screw something else). Simply changing -amd64 to amd64 or ~amd64 will _not_ fix it, it will merely make it available to screw with your system.... > > Thanks, > Mark > > -- > [email protected] mailing list -- Nick Rout <[EMAIL PROTECTED]> -- [email protected] mailing list
