Re: [gentoo-user] Using an unreleased ebuild
Am 2003.09.02 16:23 schrieb(en) Mark Knecht: Hi, There is a small app I wanted to try. I found an ebuild has been done recently and is in Bugailla: http://bugs.gentoo.org/show_bug.cgi?id=27390 I've downloaded the two files but don't know how to use them correctly. I'm guessing that I need to move it to somewhere under /usr/portage, but I do not know where to put it. Does it matter if I remember to remove it later? You sould keep it somewhere in your home directory. You can copy it somehwere in the portage tree, where you think it belongs to. Then do ebuild /path/to/file.ebuild digest emerge /path/to/file.ebuild That sould work in the most of cases. When you later user 'emerge rsync' your file gets deleted. But your programm is installed and can be deinstalled, if you want. When you get the file via 'emerge rsync', you can reuse it, but you don't have to. I'm new on gentoo, but that worked for me. Maybe other people can tell you a better way, I don't know. Martin -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Using an unreleased ebuild
On Tuesday 02 September 2003 23:23, Mark Knecht wrote: Hi, There is a small app I wanted to try. I found an ebuild has been done recently and is in Bugailla: http://bugs.gentoo.org/show_bug.cgi?id=27390 I've downloaded the two files but don't know how to use them correctly. I'm guessing that I need to move it to somewhere under /usr/portage, but I do not know where to put it. Does it matter if I remember to remove it later? How do I tell portage that this new file is there? Is there a database I have to update, or will the directory just be searched? If you put in an appropriate category under /usr/portage it will be automatically used by portage. However, it will be deleted on your next sync. The correct way to do it is to make a directory for the category under /usr/local/portage (- configurable in /etc/make.conf) and put the files in a directory under there with the name of the package. e.g. bar-1.02.ebuild should go in /usr/local/portage/foo/bar/ Regards, Jason -- [EMAIL PROTECTED] mailing list
RE: [gentoo-user] Using an unreleased ebuild
Hi, There is a small app I wanted to try. I found an ebuild has been done recently and is in Bugailla: http://bugs.gentoo.org/show_bug.cgi?id=27390 I've downloaded the two files but don't know how to use them correctly. I'm guessing that I need to move it to somewhere under /usr/portage, but I do not know where to put it. Does it matter if I remember to remove it later? How do I tell portage that this new file is there? Is there a database I have to update, or will the directory just be searched? Thanks in advance, Mark So, I've tried making a media-sound/kaconnect directory and putting the files in there. emerge -p kaconnect then tells me it's an option to install, but when I try to do an emerge kaconnect I'm told there is no Manifest file (seems to be just a warning) and then it fails saying there's no package digest file. Bravely I type ebuild /usr/portage/media-sound/kaconnect/kaconnect-1.1.1.ebuild digest and then do the emerge again. I get farther, but fail with it not finding the patch file. I then move the patch file to .../kaconnect/files, try the emerge again, and it works! Problem solved! cheers, MArk -- [EMAIL PROTECTED] mailing list
RE: [gentoo-user] Using an unreleased ebuild
Martin Jason, Thanks for your responses. I'll keep copies in my home directory to ensure nothign gets lost. How long before this sort of thing ends up in emerge sync naturally? Cheers, MArk -Original Message- From: Martin Klaffenboeck [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 02, 2003 7:36 AM To: [EMAIL PROTECTED] Subject: Re: [gentoo-user] Using an unreleased ebuild You sould keep it somewhere in your home directory. You can copy it somehwere in the portage tree, where you think it belongs to. Then do ebuild /path/to/file.ebuild digest emerge /path/to/file.ebuild That sould work in the most of cases. When you later user 'emerge rsync' your file gets deleted. But your programm is installed and can be deinstalled, if you want. When you get the file via 'emerge rsync', you can reuse it, but you don't have to. I'm new on gentoo, but that worked for me. Maybe other people can tell you a better way, I don't know. Martin -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Using an unreleased ebuild
It goes in /usr/portage/category/app where category and app are the name of the category it fits in and app is a directory named after the app. Check out /usr/portage for examples. Portage finds it automatically. You can also create a /usr/local/portage with the same structure as /usr/portage. Modify /etc/make.conf to show it exists. Then you can keep ebuilds that you want to test or create your own in the local portage. I do this to keep them out of the main portage. In either case ebuilds in either directory are picked up automatically. On Tue, 2 Sep 2003 07:23:46 -0700 Mark Knecht [EMAIL PROTECTED] wrote: Hi, There is a small app I wanted to try. I found an ebuild has been done recently and is in Bugailla: http://bugs.gentoo.org/show_bug.cgi?id=27390 I've downloaded the two files but don't know how to use them correctly. I'm guessing that I need to move it to somewhere under /usr/portage, but I do not know where to put it. Does it matter if I remember to remove it later? How do I tell portage that this new file is there? Is there a database I have to update, or will the directory just be searched? Thanks in advance, Mark -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Using an unreleased ebuild
Am 2003.09.02 16:45 schrieb(en) Mark Knecht: Martin Jason, Thanks for your responses. I'll keep copies in my home directory to ensure nothign gets lost. How long before this sort of thing ends up in emerge sync naturally? 2 weeks to 2 months, I think, sometimes longer. Depends on the ebuild you have. New ebuilds take much longer than updates. Martin Cheers, MArk -Original Message- From: Martin Klaffenboeck [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 02, 2003 7:36 AM To: [EMAIL PROTECTED] Subject: Re: [gentoo-user] Using an unreleased ebuild You sould keep it somewhere in your home directory. You can copy it somehwere in the portage tree, where you think it belongs to. Then do ebuild /path/to/file.ebuild digest emerge /path/to/file.ebuild That sould work in the most of cases. When you later user 'emerge rsync' your file gets deleted. But your programm is installed and can be deinstalled, if you want. When you get the file via 'emerge rsync', you can reuse it, but you don't have to. I'm new on gentoo, but that worked for me. Maybe other people can tell you a better way, I don't know. Martin -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Using an unreleased ebuild
On Tuesday 02 September 2003 16:23, Mark Knecht wrote: How do I tell portage that this new file is there? Is there a database I have to update, or will the directory just be searched? hi straight from /etc/make.conf : # PORTDIR_OVERLAY is a directory where local ebuilds may be stored without # concern that they will be deleted by rsync updates. Default is not # defined. #PORTDIR_OVERLAY=/usr/local/portage wanna give this a try ?? Azhdeen -- [EMAIL PROTECTED] mailing list
