<div class="gmail_quote">2009/5/29 Dušan Stefanović <span dir="ltr"><<a href="mailto:stefanovic.dusan@gmail.com">stefanovic.dusan@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I'm not trying to hijack this thread, but there is another question<br>
related to this discussion. What about i486 packages that are created<br>
for slackware64?<br>
slackware64 is multilib, so it is perfectly legal to do this. How<br>
should I name package that has 32bit binary inside, but is created for<br>
slack64?<br>
<br>
name-version-x86_64-build or name-version-i486-build or<br>
name-version-i486-build_s64?<br>
<br>
Long time ago slack packages had different name scheme than today (you<br>
can see it here:<br>
<a href="ftp://ftp.slackware.no/pub/linux/slackware/slackware-4.0/slakware/d1/" target="_blank">ftp://ftp.slackware.no/pub/linux/slackware/slackware-4.0/slakware/d1/</a><br>
). It was name.tgz, then after few releases it was changed to what we<br>
know today name-version-arch-build. Pat already has problem with this<br>
naming scheme, because it doesn't have slackware version (you can see<br>
that at any slack mirror, just look at patches directory). I know that<br>
it is for Pat to decide and not for as, but maybe it is time for<br>
change. pkgtools are already changed for next release, so maybe it is<br>
possible to add slackware version to naming scheme.<br>
<br>
regards,<br>
<font color="#888888">ds<br>
</font><div><div></div><div class="h5"></div></div></blockquote><div> <br>Yes, although the naming scheme is not the mission of this thread but I think it *may* provide a solution for this problem. Especially for the ones that think Slackware64 is just a other *version* of slackware but not the stoke slackware in x86_64 arch.<br>
<br>But this will bring an other problem. What if the both the files *and* the directory structure are arch independent?(bash-completion as an example, although it not in slackware64 now) It's also non-sense to have two names with one package that exactly the same.<br>
</div></div><br>-- <br>Cheers,<br>Grissiom<br>