On Thu, Jun 21, 2012 at 12:27:04PM -0400, Mikhail T. wrote: > On 21.06.2012 11:37, Wesley Shields wrote: > > The release in our ports tree is not recommended upstream anymore. > > Quoting the upstream webpage: "Take note they [old releases] won't > > usually work with recent LLVM and GNUstep releases." > Do we have these recent LLVM and GNUstep releases in the tree already?
In base, yes I believe so. Older, yet still supported FreeBSD releases, would require using what's in the ports tree. Please don't take my word on any of this as it was only what I read from their webpage as I don't use any of these ports. > > As the port is unmaintained and the version in our tree is not > > recommended for use anymore it was deprecated. Sure, the reason could be > > more clear. I will commit an update that reflects that to make it more > > clear. > > > > If you would like to see this port remain in the tree I recommend > > adopting it and keeping it in working order (first step is to update it > > to a recommended release). > The chance of a new maintainer stepping up may increase, if the > "deprecation" message states something like "Update to a new release > is required"... And, of course, a more generous expiration time would > be needed. These ports are a legion... I will update the deprecation message shortly. I will also update the expiration date if someone is willing to at least verbally commit to working on an update. I see no point in pushing the expiration date back if nobody is going to do the work to keep it properly maintained. If someone steps up after the port has been removed I will happily pull it out of the Attic for that person. -- WXS _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"