this post was submitted on 20 Oct 2024
626 points (87.4% liked)

Technology

59709 readers
1839 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 14 points 1 month ago (1 children)

They literally posted that this is a packaging bug and will be resolved.

[–] [email protected] 2 points 1 month ago (1 children)
[–] [email protected] 1 points 1 month ago* (last edited 1 month ago)

Just because I didn't see a response on this one, you might have read it already in other comments but the packaging bug is a cop out. They are still intending to migrate over to the proprietary SDK, and it will eventually become a requirement for the platform. The only difference was that at the state of the project it wasn't supposed to be a requirement in order to compile, but they do still very intently have a restrictive license on the SDK and you aren't allowed to use the sdk outside of the project. meaning that it has to be present for the program to work and that you're not allowed to use it in other programs.

Why they call it a packaging bug I'm not sure because the end result is the same the package is required for the program to work and that package that is required is not GPL

That being said some other comments have gone a little bit more in detail on it and might be a little more descriptive than me