| Summary: | vimbrowser-1.1.ebuild (New Package) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Moshe Kamensky <kamensky.fb> |
| Component: | New packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | enhancement | CC: | kamensky.fb, vim |
| Priority: | High | Keywords: | EBUILD |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://www.vim.org/scripts/script.php?script_id=1053 | ||
| Whiteboard: | sunrise suggested | ||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
vimbrowser-1.1.ebuild
synmark-0.2.ebuild modified vimbrowser-1.1.ebuild modified synmark-0.2.ebuild repackaged vimbrowser-1.1.tar.bz2 |
||
|
Description
Moshe Kamensky
2005-03-15 13:59:23 UTC
Created attachment 53564 [details]
vimbrowser-1.1.ebuild
Created attachment 53565 [details]
synmark-0.2.ebuild
A dependency of vimbrowser-1.1.ebuild
Hrm, we can't reliably use vim.org SRC_URIs so we'll have to mirror ourselves. I think the perl dep needs checking too -- libperl might be better? I'll take this once I'm done breaking^W moving sys-apps unless someone else wants to. Ok, here's another try. I attach two modified ebuilds, and a re-packaged vimbrowser. The perl dependency is needed for the command line script, vimbrowse. Otherwise, I guess libperl is enough. Maybe this can depend on another use flag. What I don't is how to depend on vim with a perl use flag. Is it possible? Created attachment 53605 [details]
modified vimbrowser-1.1.ebuild
Created attachment 53606 [details]
modified synmark-0.2.ebuild
Created attachment 53609 [details] repackaged vimbrowser-1.1.tar.bz2 package to use with vimbrowser-1.1.ebuild, attachment #53605 [details] Sadly, we can't currently depend upon packages built with a certain flag enabled. That's a rather long-standing feature requirement that still hasn't been implemented... (this is an automated message based on filtering criteria that matched this bug) 'EBUILD' is in the KEYWORDS which should mean that there is a ebuild attached to this bug. This bug is assigned to maintainer-wanted which means that it is not in the main tree. Hello, The Gentoo Team would like to firstly thank you for your ebuild submission. We also apologize for not being able to accommodate you in a timely manner. There are simply too many new packages. Allow me to use this opportunity to introduce you to Gentoo Sunrise. The sunrise overlay[1] is a overlay for Gentoo which we allow trusted users to commit to and all users can have ebuilds reviewed by Gentoo devs for entry into the overlay. So, the sunrise team is suggesting that you look into this and submit your ebuild to the overlay where even *you* can commit to. =) Because this is a mass message, we are also asking you to be patient with us. We anticipate a large number of requests in a short time. Thanks, On behalf of the Gentoo Sunrise Team, Jeremy. [1]: http://www.gentoo.org/proj/en/sunrise/ [2]: http://overlays.gentoo.org/proj/sunrise/wiki/SunriseFaq According to the link given in the URL box, the latest commit for this project dates back to 2005. We can consider this plugin somewhat dead and/or unmaintained. It won't be added to Portage. Closing. |