Replies: 3 comments 1 reply
-
|
Sorry, I have no experience with rpm or building Python packages for it. |
Beta Was this translation helpful? Give feedback.
-
|
tho IN an rpm build env, the install is simply the question is how/where to "tell" that^^ to find/link system-installed libs. regardless of the build env. atm, i suspect the issue 'involves' the torchaudio/torio prereq. but, it first manifests only in the coquit-tts build. |
Beta Was this translation helpful? Give feedback.
-
|
Are you sure simply installing the package is enough and no specific build is necessary? Maybe the following is helpful: https://docs.fedoraproject.org/en-US/packaging-guidelines/Python |
Beta Was this translation helpful? Give feedback.
-
|
well, there are certainly some packaging specifics. my goal is a completely isolated install -- built in a python venv, including a python build, all prereqs -- including ffmpeg* -- and coqui-tts itself. all packaged in a non-system dir -- e.g., in this way i can (hope?) to control the deps, and NOT pollute -- or be polltued by -- the distro Python env. i do it all the time for other Py* pkging. this one's simply giving me a headache finding the source of -- and quashing -- those multiple missing deps. |
Beta Was this translation helpful? Give feedback.
-
i'm working on an rpm build of coqui-tts, on
i'm building in a isolated venv.
in my
mockbuild venv, i'veand
these prereqs exist
the install completes with no errors
but on rpm install,
where, on install target, e.g.,
neither my build env, nor the target env, have those missing lib deps.
some logic -- yet TBD ... -- in the coqui-tts install process is pulling them in.
where can I specify/override them? so that the built/to-be-installed coqui-tts rpm links only to the libs available on source/target?
Beta Was this translation helpful? Give feedback.
All reactions