SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Yeah - I've already complained about this more than once in more than one place (including Pat) -
Did you stomp your feet? Maybe I missed that.
Quote:
Originally Posted by slakmagik
I gather one or both of these things will be fixed in a little while, though. I patch it (delete a line) to fix the builtin menu but I doubt Pat would want to do that. But the docdir cleanup needs to happen in the SlackBuild at least for now.
The fix for fvwm-menu-directory is in CVS. I won't be doing *anything* else, docdir or otherwise until various FVWM-housekeeping things happen. Hopefully that won't be too soon now.
Originally Posted by slakmagik in #fvwm on 2011-04-16
01:24:18< slakmagik> anyway, I also have two packaging issues - these aren't new but the other issue got me here: 1) '--docdir' is ignored though '--prefix' and '--mandir' and the like work
01:24:55< slakmagik> 2) there should be a way to separate the config file and the rest of what defaults to /usr/local/share
Granted, jaimos was the only one who replied at the time but you never miss the opportunity to make a snide remark about anything else I say, so I don't know how you missed this. Especially as you replied to the other issue. I guess the purely broken --docdir issue didn't give you any ammo with which to insult me, so you forgot about it.
Quote:
Originally Posted by ThomasAdam
The fix for fvwm-menu-directory is in CVS. I won't be doing *anything* else, docdir or otherwise until various FVWM-housekeeping things happen. Hopefully that won't be too soon now.
Which is why I said "I gather one or both of those things will be fixed" but that the docdir issue needed to be worked around in Slackware now.
Last edited by slakmagik; 04-24-2011 at 06:39 PM.
Reason: clarify irc date
I don't want to get involved in a fight that I didn't start (it's no fun to insult people unless I have a personal stake in watching tears fall), but I do want say this to Thomas Adam: thanks for posting/responding/watching the forums here. It's not often that we see a lot of upstream presence here (or anywhere else, it sometimes seems), so I wanted to make sure you were aware that it's appreciated. I won't promise to always say stuff that you like, but thanks for being here to read it :-)
I wonder if the release date is actually going to be April 28th? This would be a nice contrast with a well-known Linux distro that is promising a big release on that very day .
EDIT: Umm, it turns out the link below has gone 403 since I posted it. Sorry, folks, however this really was the state of the ChangeLog at the time, and it is still accessible via Google Reader and the SlackAgg feed:
Thanks to everyone who pitched in on this release: the Slackware team,
the folks producing upstream code, and linuxquestions.org for providing
a great forum for collaboration and testing.
The ISOs are off to be replicated, a 6 CD-ROM 32-bit set and a dual-sided
32-bit/64-bit x86/x86_64 DVD. Please consider supporting the Slackware
project by picking up a copy from store.slackware.com. We're taking
pre-orders now, and offer a discount if you sign up for a subscription.
As always, thanks to the Slackware community for testing, suggestions,
and feedback. :-)
Have fun!
Last edited by 55020; 04-25-2011 at 04:15 AM.
Reason: Ick, the linkie is duff :-(
Ok ok they were elves, I got overexcited, gee thanks a heap for the downmodding :-\
1) Someone didn't appreciate you publicising the leaked information.
or
2) They were too dumb to spot it as leaked information and thought you were just making it up in an attemp to troll.
or
3) You were making it up and trolling and deserve the downmodding.
Guess we'll find out in about 4 and a bit hours time.
For avoidance of doubt, GazL's quote is the 'reason' tag of the first edit I made to the above post; the post that you now see above is the second edit, which preceded GazL's post by a few minutes.
As I said above, "Apologies to the Team if this wasn't supposed to be visible yet", but it was visible, and I posted in good faith. Hey, it's 10am on a public holiday; what else is there to do but hammer those RSS feeds?
2) They were too dumb to spot it as leaked information and thought you were just making it up in an attemp to troll.
Did he himself spot it as leaked info?
The post read as if the release had already happened.
You don't need much to upset a Slacker who's waiting for a new release.
Did he himself spot it as leaked info?
The post read as if the release had already happened.
No, I was surmising that it was a leak based on the timestamp 13.37 UTC which hasn't happened yet.
Of course, that doesn't actually mean it's an accurate leak. The date/time could have been subject to change since that was written, so we may not find out in about 4 hours time.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.