files/. Most often it's just configuration stuff, as you've said .
I believe LXDE is dead. The developers moved to a QT version.Is there a bigger issue with the LXDE port and all of the related ports?
I had feared that, not because of the DE itself but I really like graphics/gpicview as a quick little viewer because you can arrow through every graphic in a directory, plus you have to just hit "esc" to exit the app. Very keyboard friendly and easy to use. I can use graphics/feh but a script is needed for it to have the same functionality. Thanks for the information, appreciate it.I believe LXDE is dead. The developers moved to a QT version.
Even if its not dead there is enough doubt to cause mayhem. Too bad as I liked thier spin on openbox.
It can vary wildly depending on what condition the upstream source is in terms of portability and assessing the portability for a completely new piece of software can be a real challenge. You can get a very good picture of how much FreeBSD local patching a port requires by looking at the files subdirectory of a port, everything named as patch-* is automatically applied to extracted pristine source.Forgive me is this question is a bit noobish: maintaining ports is not a development effort is it? I mean it does not involve coding on the port in question, other than modifying the Makefile or pkg-descr or other related files, correct? I see port maintenance as more of a configuration management function but wanted to ask. I was a developer for a little over 10 years but have gotten out of it and do not wish to get back into coding. Thanks in advance.
Reaction score: 909
Reaction score: 936
The FreeBSD Porter's Handbook provides the answer:What are the precedents to have a port removed from the tree? Between those unmaintained ports may have many dead projects what probably would be more interesting to have them removed, after a careful look, than leave them unmaintained.
LXDE looks to still be maintained/aliveThe only thing I can determine is that the author appears to be the same or in the same group that wrote LXDE and related ports, all of which appear to be unmaintained. What should I do at this point? Is this simply a matter of updating the maintainer to me and submitting a PR? Is there a bigger issue with the LXDE port and all of the related ports?
The link in the pkg-descr doc takes you to the correct site but most of the site links don't work and it's a dead project since they've moved on to audio/xmms2. That RockLight plugin that causes the Thinklight of a Thinkpad to flash to the beat of the music is just what I needed, too.I noticed an error on the xmms link.
But when the word xmms is clicked on your post, it gives a error on freshportsThe link in the pkg-descr doc takes you to the correct site but most of the site links don't work and it's a dead project since they've moved on to xmms2. That RockLight plugin that causes the Thinklight of a Thinkpad to flash to the beat of the music is just what I needed.
Beings xmms is no longer being developed, there won't be any upstream versions for a maintainer to work from should a vulnerability or other problem require a version bump from 1.2.11. So becoming a maintainer for it would be a moot point, from what I understand of the portion of the Porters Handbook I've read so far.
Best save the distfile to a USB if you want to keep it should problems arise and it be removed from the ports tree
Your own link to audio/xmms2 shows the same link mine does.Create a link to a ported program's page on Freshports. Requires category and port name separated by a slash.
Reaction score: 500
Reaction score: 293