On Sat, Oct 23, 2010 at 5:45 PM, Niels Horn <[email protected]> wrote:
> On Sat, Oct 23, 2010 at 4:48 PM, Stuart Winter <[email protected]> wrote:
>>
>>> This probably happens because the packages have an ARCH setting of
>>> "armv5t" and SlackPkg looks for "arm".
>>>
>>> Should I report this to PiterPunk? It seems to be a specific ARMedslack
>>> issue.
>>
>> Yes slackpkg should handle it - unless these packages have their armv4
>> compatability returned (it was removed from the code), then I will
>> continue to give them the arch value they have now.
>>
>> I guess he could just match on "arm*". I'm not sure if there are any
>> downsides to this, but given that we only have one ARM port now (rather
>> than the oldabi), I don't see any problems here.
>
> OK, I'll write to PiterPunk. It might be a simple change in the
> configuration file, or might need a patch.
> I'll investigate this a bit more, to save him some work ;)
>
> Niels
>
OK, I patched /usr/libexec/slackpkg/core-functions.sh and this works fine:
--- core-functions.sh_orig 2010-05-01 20:10:33.000000000 -0300
+++ core-functions.sh 2010-10-23 22:02:55.799755000 -0200
@@ -122,7 +122,7 @@
PKGMAIN=${PKGMAIN:-slackware}
;;
arm*)
- ARCH=arm[el]*
+ ARCH=arm[v5t]*
SLACKKEY=${SLACKKEY:-"ARMedslack Security
(ARMedslack Linux Project Security) <[email protected]>"}
PKGMAIN=${PKGMAIN:-slackware}
;;
(to avoid problems with line-breaking etc, also attached as a file...)
I could not find any "armel" packages, so this should be safe.
I'll send the patch to PiterPunk as well.
Regards,
Niels
--- core-functions.sh_orig 2010-05-01 20:10:33.000000000 -0300
+++ core-functions.sh 2010-10-23 22:02:55.799755000 -0200
@@ -122,7 +122,7 @@
PKGMAIN=${PKGMAIN:-slackware}
;;
arm*)
- ARCH=arm[el]*
+ ARCH=arm[v5t]*
SLACKKEY=${SLACKKEY:-"ARMedslack Security (ARMedslack Linux Project Security) <[email protected]>"}
PKGMAIN=${PKGMAIN:-slackware}
;;
_______________________________________________
ARMedslack mailing list
[email protected]
http://lists.armedslack.org/mailman/listinfo/armedslack