[Bug 212530] x11-wm/fluxbox-devel: Revive port
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue Oct 25 15:03:31 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212530
lightside <lightside at gmx.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #174592|0 |1
is obsolete| |
--- Comment #3 from lightside <lightside at gmx.com> ---
Created attachment 176146
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=176146&action=edit
Proposed patch based on copied x11-wm/fluxbox port (since 421576 revision)
(In reply to comment #2)
> Too many changes in the diff which are only of historic value. Try rebasing
> after |svn cp x11-wm/fluxbox{,-devel}| or convert to a slave port.
Ok, I attached new patch, which based on copied x11-wm/fluxbox port (since
ports r421576) to x11-wm/fluxbox-devel.
(In reply to comment #1)
> Also I didn't add XINERAMA to OPTIONS_DEFAULT.
The XINERAMA in OPTIONS_DEFAULT was migrated from x11-wm/fluxbox port.
(In reply to comment #2)
> Revived ports are treated as new and won't be accepted unless a maintainer is
> assigned.
This wasn't the case for bug 198025, related to revived textproc/xxdiff and
textproc/xxdiff-scripts ports.
(In reply to comment #2)
> If the maintainer isn't the same as submitter approval is required.
> mezz at currently doesn't maintain any port and stopped committing since
> ports r331734.
I understood. I changed MAINTAINER to ports@, as I said in comment #0. My
reasoning was explained in bug 211814 comment #18. I created devel version of
port as intermediate solution before new Fluxbox release version (or for tests
of development version(s)). If there are no other interest about such a port in
FreeBSD ports, then this PR may be closed. "The batteries are not included", as
someone said.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list