EricGao888 commented on PR #10337:
URL: 
https://github.com/apache/dolphinscheduler/pull/10337#issuecomment-1159365199

   > > > and we still have discussion in [#10337 
(comment)](https://github.com/apache/dolphinscheduler/pull/10337#discussion_r896857846),
 I wonder whether conda have some command like `import` same as docker's 
`docker import` to import and then `conda activate`?
   > > 
   > > 
   > > I haven't found such things so far. However, using `source` for unpacked 
conda env seems to be the only way I could find on 
[Conda-Pack](https://conda.github.io/conda-pack/) official page.
   > > 
![image](https://user-images.githubusercontent.com/34905992/173829371-9ea3b6d5-da1a-40b4-8344-5c7db1399c6e.png)
   > 
   > Yeah, I can not find either, I think maybe we should use `source` to 
activate the env template, WDYT @EricGao888 @SbloodyS
   
   Yes, IMHO, there is no perfect solution here to avoid using `source` while 
providing good user experience at the same time. This is a trade-off. I think 
we could give user this option but add some notice about `source` command in 
docs. If they have concerns about it, they could choose not to use it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to