如何修改Flutter Linux软件包（.deb或.rpm）的目录结构以符合标准规范？

Got it, let's tackle this step by step since you're aiming for Debian/Ubuntu official repo compliance with FHS (Filesystem Hierarchy Standard) standards. We'll use fpm alongside tools like patchelf to adjust Flutter's default path expectations to match standard system directories.

核心思路 #

Flutter's Linux bundle uses relative paths for dependencies (./lib) and assets (./data). We need to:

1. Modify the executable to look for shared libraries in /usr/lib/<package_name>
2. Ensure the app loads assets from /usr/share/<package_name>/data
3. Organize all files into a FHS-compliant structure before packaging with fpm

步骤1：编译Flutter应用到Release Bundle #

First, build your app's release bundle as usual:

flutter build linux --release

This creates the bundle at build/linux/x64/release/bundle/ with:

• Your executable (e.g., my_flutter_app)
• data/ (assets)
• lib/ (shared dependencies)

步骤2：调整可执行文件的库查找路径 #

Flutter's executable expects shared libraries in ./lib relative to itself. We'll use patchelf to set a rpath that points to /usr/lib/<package_name> (replace <package_name> with your app's actual name, e.g., my_flutter_app).

1. Install patchelf first:

   # Debian/Ubuntu
   sudo apt install patchelf
   # Fedora/RHEL
   sudo dnf install patchelf
   

2. Modify the executable's rpath:

   patchelf --set-rpath '$ORIGIN/../lib/<package_name>' build/linux/x64/release/bundle/<package_name>
   

   The $ORIGIN variable resolves to the executable's directory (which will be /usr/bin), so ../lib/<package_name> translates to /usr/lib/<package_name>.

步骤3：创建Wrapper脚本（处理资产路径） #

Flutter apps load assets from a relative ./data directory by default. Instead of hardcoding paths in your app, use a wrapper script as the system entry point to set the correct asset path via an environment variable.

1. Create a temporary packaging directory structure matching FHS:

   mkdir -p build/package/usr/bin
   mkdir -p build/package/usr/share/<package_name>
   mkdir -p build/package/usr/lib/<package_name>
   

2. Create the wrapper script at build/package/usr/bin/<package_name>:

   cat > build/package/usr/bin/<package_name> << EOF
   #!/bin/bash
   # Set the path to Flutter assets
   export FLUTTER_ASSET_PATH=/usr/share/<package_name>/data
   # Execute the actual app binary with all passed arguments
   exec /usr/lib/<package_name>/<package_name> "\$@"
   EOF
   

3. Make the script executable:

   chmod +x build/package/usr/bin/<package_name>
   

步骤4：Copy Files to FHS Structure #

Move all bundle files into your temporary packaging directory:

# Copy shared libraries to /usr/lib/<package_name>
cp -r build/linux/x64/release/bundle/lib/* build/package/usr/lib/<package_name>/

# Copy assets to /usr/share/<package_name>/data
cp -r build/linux/x64/release/bundle/data build/package/usr/share/<package_name>/

# Copy the modified executable to /usr/lib/<package_name>
cp build/linux/x64/release/bundle/<package_name> build/package/usr/lib/<package_name>/

步骤5：Add Desktop Integration（Debian/Ubuntu最佳实践） #

To get your app listed in the system menu, add a .desktop file:

1. Create build/package/usr/share/applications/<package_name>.desktop with:

   [Desktop Entry]
   Name=Your App Name
   Comment=A short description of your application
   Exec=<package_name>
   Icon=/usr/share/<package_name>/data/flutter_assets/icons/app_icon.png
   Terminal=false
   Type=Application
   Categories=Utility;GTK;Application; # Adjust categories to match your app
   

2. Ensure the icon path points to your app's actual icon in the assets directory.

步骤6：Package with fpm #

Now use fpm to build your .deb and .rpm packages.

Build .deb Package

fpm -s dir -t deb \
  -n <package_name> \
  -v 1.0.0-1 \ # Follow Debian versioning: <upstream_version>-<debian_revision>
  --description "Your Flutter application description" \
  --maintainer "Your Name <your.email@example.com>" \
  --depends libgtk-3-0 \
  --depends libglib2.0-0 \
  --depends libjsoncpp1 \
  # Add any other system dependencies your app requires (check with `ldd` on the executable)
  -C build/package/ \
  usr/bin/<package_name> \
  usr/share/<package_name> \
  usr/lib/<package_name> \
  usr/share/applications/<package_name>.desktop

Build .rpm Package

fpm -s dir -t rpm \
  -n <package_name> \
  -v 1.0.0 \
  --description "Your Flutter application description" \
  --maintainer "Your Name <your.email@example.com>" \
  --depends gtk3 \
  --depends glib2 \
  --depends jsoncpp \
  # Add RPM-specific dependencies
  -C build/package/ \
  usr/bin/<package_name> \
  usr/share/<package_name> \
  usr/lib/<package_name> \
  usr/share/applications/<package_name>.desktop

步骤7：Validate the Package #

Test installing the package and verify:

• The executable runs without errors
• Assets load correctly (e.g., icons, images)
• The app appears in the system menu
• Shared libraries are found (use ldd /usr/lib/<package_name>/<package_name> to check)

额外注意事项（Debian/Ubuntu官方仓库合规） #

• Versioning: Follow Debian's versioning scheme (<upstream_version>-<debian_revision>)
• Copyright: Add a copyright file to usr/share/doc/<package_name>/ with your app's license info
• Changelog: Create a changelog file in the same directory to track package changes
• Dependencies: Ensure all dependencies are available in Debian/Ubuntu's main repository (avoid non-free software if targeting official repos)
• Permissions: Ensure all files have correct permissions (executables: 755, assets: 644, etc.)

内容的提问来源于stack exchange，提问作者A_Singh7