Re: [Slackbuilds-users] Shouldn't KeePass (mono apps in general) be ARCH=noarch?

[Andreas Guldstrand]

On 29 October 2016 at 21:11, Thomas Szteliga  wrote:
> On 10/29/2016 08:37 PM, B Watson wrote:
>> Example: a lot of Perl packages install only perl code, nothing native,
>> but the install path is different (lib vs. lib64) so they can't use
>> noarch.

Actually, a lot of perl packages don't actually use lib/lib64 at all,
but are still not marked noarch in SBo.

I found this out when I carefully checked a bunch of perl submissions
of mine if they used an arch-dependent directory at all, and when they
didn't I marked them as noarch ... and then that was changed after I
submitted.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Shouldn't KeePass (mono apps in general) be ARCH=noarch?

[Thomas Szteliga]

On 10/29/2016 08:37 PM, B Watson wrote:
> On 10/29/16, Thomas Szteliga  wrote:
>> Now I'm thinking that KeePass itself should be noarch too...
>> Am I right? It's a pure mono application (binary).
> If there are no native (ELF) binaries, the only other thing to watch
> out for is LIBDIRSUFFIX. If it installs stuff in /usr/lib on 32-bit and
> /usr/lib64 on 64-bit, you'll want to get rid of that (/usr/share/$PRGNAM
> is probably better).


I think this /usr/share/$PRGNAM in this case is much better
than /usr/lib/$PRGNAM. I've seen this on Arch Linux.
Fedora ships KeePass with defined ARCH and in /usr/lib
(also the x86_64 pkg) but I see there's another thing,
the Slackware pkg is coming with KeePassLibC32.dll and KeePassLibC64.dll
and ShInstUtil.exe, which are probably
not needed (not found in fedora's rpm). I'll check this
before posting a noarch Slackbuild.


> The test is whether the same binary package runs correctly on either
> 32-bit or 64-bit.
> Example: a lot of Perl packages install only perl code, nothing native,
> but the install path is different (lib vs. lib64) so they can't use
> noarch.


All KeePass files (except icons) land in /usr/lib/KeePass/
on both - x86 and x86_64.


> ...and, you have just made me realize that the 'domination' build I just
> submitted should be noarch also (it's pure Java).


:-)


-- 
Thomas Szteliga




smime.p7s
Description: S/MIME Cryptographic Signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Shouldn't KeePass (mono apps in general) be ARCH=noarch?

[B Watson]

On 10/29/16, Thomas Szteliga  wrote:

> Now I'm thinking that KeePass itself should be noarch too...
> Am I right? It's a pure mono application (binary).

If there are no native (ELF) binaries, the only other thing to watch
out for is LIBDIRSUFFIX. If it installs stuff in /usr/lib on 32-bit and
/usr/lib64 on 64-bit, you'll want to get rid of that (/usr/share/$PRGNAM
is probably better).

The test is whether the same binary package runs correctly on either
32-bit or 64-bit.

Example: a lot of Perl packages install only perl code, nothing native,
but the install path is different (lib vs. lib64) so they can't use
noarch.

...and, you have just made me realize that the 'domination' build I just
submitted should be noarch also (it's pure Java).
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] Shouldn't KeePass (mono apps in general) be ARCH=noarch?

[Thomas Szteliga]

Hello,

lately I posted an update for KeePass
https://slackbuilds.org/repository/14.2/misc/KeePass/
and now I'm creating a SlackBuild for KeePassHttp, which
is a plugin for KeePass and this plugin is a pure plgx file,
(no compilation needed) so the Slackbuild will contain
ARCH=noarch.

Now I'm thinking that KeePass itself should be noarch too...
Am I right? It's a pure mono application (binary).

https://slackbuilds.org/slackbuilds/14.2/misc/KeePass/KeePass.SlackBuild

Just let me know and I'll post an updated Slackbuild.

-- 
Thomas Szteliga




smime.p7s
Description: S/MIME Cryptographic Signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/