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.
First off, I really hate the shily make system. That being said, I just spent quite a bit of time screwing with cdrtools to make it multilib compliant.
Look it over or not, just thought I'd toss it out in case anyone wanted to add
LIBDIRSUFFIX="64"
to it...
Code:
sed -i "s/^COPTOPT=.*/COPTOPT=$SLKCFLAGS/g" RULES/cc-*.rul
grep -rl '/etc/default/cdrecord' . | xargs sed -i \
's@/etc/default/cdrecord@/etc/cdrecord.conf@g'
grep -rl 'share/doc' . | xargs sed -i 's@share/doc@doc@g'
find . -name "*.mk" | xargs sed -i \
-e "s@lib/siconv@lib$LIBDIRSUFFIX/siconv@g" \
-e "s/INSDIR=\s*lib\s*$/INSDIR=lib$LIBDIRSUFFIX\n/g"
sed -i "s@lib/siconv@lib$LIBDIRSUFFIX/siconv@g" libsiconv/sic_nls.c \
mkisofs/diag/isoinfo.c \
mkisofs/mkisofs.c \
libsiconv/tables/Makefile
INS_BASE=/usr DEFINSGRP=root make -e $NUMJOBS || exit 1
# Without this second run, cdda2wav is skipped...
INS_BASE=/usr DEFINSGRP=root make -e || exit 1
INS_BASE=$PKG/usr DEFINSGRP=root make -e install || exit 1
cat cdrecord/cdrecord.dfl > $PKG/etc/cdrecord.conf.new
rm -rf $PKG/usr/{sbin,doc/rscsi,man/man1/rscsi.1}
Well, for the siconv stuff as it all appears to be text files, shouldn't that really be stored somewhere under /usr/share, rather than /usr/lib(64 or otherwise)?
I've never really liked the idea of programs dumping stuff other than their shared libraries under /usr/lib[64]/<programname>. It just feels untidy to me.
And don't even get me started on all the crap under /usr/lib/rpm!
These aren't really Slackware's fault though. It's upstream being untidy. In a lot of the cases the stuff that gets dumped into /usr/lib/<programname> looks like it actually belongs somewhere in /usr/share, /usr/libexec and on odd occasions even /etc.
I commend you for caring about this jong357. It's something that gets under my skin too.
I've never really liked the idea of programs dumping stuff other than their shared libraries under /usr/lib[64]/<programname>.
This is even worse: samba dumps crap directly to /usr/lib[64] with names like /usr/lib64/fr.msg containing text files (translations for SWAT). The name of the file or the directory give no clue to what program the file is for. All programs could install French translations to the same filename.
I stopped doing that a long time ago because I typically never got a response. Seems the "official" Slackware forums are no different. The PyQT bug still exists and so does $ARCHTYPE in liloconf.....
Don't mean to be a dick but this is insanely sloppy.... How long does it take for a team (ie - plural) to fix things when one person manages to keep things tidy on his own bootstrapped system (ie - me)?
Oh yea... This is why I quit using Slackware. I remember now. You guys are still running a shadow on 13.0 that's literally from 2003 or before. I've been using SHA512 for eons now but Slackware can't even use anything but MD5...
It's just really absurd. I'll shut up and take my toys home now. It's just really a shame when people don't pay attention to detail. Bothers me really bad for some reason... Bothers me even more when I take the time to report bugs but they go unfixed for months.
Well, for the siconv stuff as it all appears to be text files, shouldn't that really be stored somewhere under /usr/share, rather than /usr/lib(64 or otherwise)?
These aren't really Slackware's fault though. It's upstream being untidy.
Yes, but it is Pat and company that need to be held accountable for fixing this stuff and not pushing out the same upstream garbage to the end users. Hey.... That's called making and maintaining a distro. Joerg Schilling has his head so far up his arse that things like this will never be "fixed" upstream.
So instead of complaining about something having to be in /etc/default, why not change it like I did above? Problem solved. Now you have a nice little /etc/cdrecord.conf file....
I dunno.
For that matter, I'm still curious as to how the kernel-headers package is made along with cxxlibs.... It's a mystery I guess. For all I know, they come from a fedora rpm and are just repackaged in tgz format...
Yes, but it is Pat and company that need to be held accountable for fixing this stuff and not pushing out the same upstream garbage to the end users. Hey.... That's called making and maintaining a distro.
Yes, I take your point jong, and as I said above, I also find this stuff frustrating, however, the opposite extreme of changing too much leads to things like the debian SSL fiasco, so care is needed.
Slackware has always been conservative about the changes it makes to what upstream provides. The best you can do is send in a patch and hope to convince Pat to agree to use it. And yes, it's very frustrating when you don't get a response. If you don't get satisfaction then you either have to live with it, make the changes locally, or move on to something else.
So far I do the first two of those. Occasionally, frustration gets the better of me and I feel like doing the third, but short of 'rolling my own' Slackware is still the best match for what I'm looking for, and no distro is perfect.
I hate to see this thread derail into grumpiness and frustration because I think there's a valid point or two here. Naturally, there's nothing stopping any of us from rebuilding the package using your patch -- even if Pat and the team do not. So, thanks for the contribution.
FWIW, src2pkg has some functions for correcting the location of files. You might want to look into that utility a bit.
By the way, I've been reading your modification of the DIY Linux reference build. I'm learning a lot. Thank you.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.