Date: Mon, 4 Jan 2021 22:57:19 +0100 From: Guido Falsi <mad@madpilot.net> To: Andrea Venturoli <ml@andreaventuroli.it>, xfce@freebsd.org Subject: Re: XFCE upgraded to 4.16 Message-ID: <f9df4884-d392-eb9b-4200-00160047d312@madpilot.net> In-Reply-To: <d24a4997-0fbe-5d8c-7d94-a8f354f1be41@andreaventuroli.it> References: <46a21428-a640-f895-0f3b-f44c09497bf5@madpilot.net> <747ecac6-6d60-6143-1ae1-47801299b59b@netfence.it> <1502a321-02c0-13e9-16b3-6f11da9de3af@madpilot.net> <47ede65d-817a-8d80-a582-660d43ac6ac3@andreaventuroli.it> <ee9f59de-8814-cf6d-cf8a-ff13a88dccd2@madpilot.net> <7f9cc4b4-81aa-354e-4bf5-c4867ca51d13@madpilot.net> <6e8ec4ab-0382-7eae-e623-5f48df2f10c7@andreaventuroli.it> <381c702b-c1a7-ac99-c9bb-82fd08ef3eba@madpilot.net> <d24a4997-0fbe-5d8c-7d94-a8f354f1be41@andreaventuroli.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04/01/21 19:43, Andrea Venturoli wrote: > On 1/4/21 6:51 PM, Guido Falsi wrote: > >> They are marked BROKEN, so not being build anyway. At least in theory >> port rules require a deprecation period for ports before removal, >> including BROKEN ones. > > Sorry, this makes sense, they should have been marked BROKEN, not removed. > However, of the ports I cited: > _ audio/xfce4-mixer was removed This one was marked as deprecated in r540614 on Jun 27. AN expiration date was NOT set because the exact date of release of XFCE 4.16 was unknown. Also even having a slight idea when it would be (the release slipped two times anyway) I could not know for sure when I would have had the port of the release ready. > _ deskutils/xfce4-generic-slider was marked BROKEN; This one is not maintained by xfce@. The decision to mark it as BROKEN was taken together with the maintainer. It's his call if he wants to remove it, deprecate it or whatever. > _ sysutils/xfce4-kbdleds-plugin was left untouched. This one builds fine and links with gtk3, are you sure it is not working? AFAIK it should work correctly. >> Someone could step in and fix them, for example, this is easier if the >> port is not actually removed. > > The way I understand it, they are not fixable (of course short of a > major rewriting). This does not mean that nobody could step in. > If they are supposed to be fixable, I might even try and see if I can > help (although I won't promise anything). We have already been informed that work is ongoing to revive mixer. Unluckily it is improbable it will be ready in less than a month. Anyway Broken ports in the tree don't cause any strain and cost nothing. The package builder simply skips them. Since we are using a revision control removing them saves no disk space. I don't see a problem in having them stay in the tree deprecated for a few weeks until they are (semi)automatically removed. -- Guido Falsi <mad@madpilot.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f9df4884-d392-eb9b-4200-00160047d312>