can a snap package depend on a .deb package provided by the distro?












0















Can a snap be built in a way such as, when the user tries to install it, the snap also installs another package? For example, wget. Thanks.






apt package-management snap deb packaging







share|improve this question



























    0















    Can a snap be built in a way such as, when the user tries to install it, the snap also installs another package? For example, wget. Thanks.






    apt package-management snap deb packaging







    share|improve this question

























      0












      0








      0








      Can a snap be built in a way such as, when the user tries to install it, the snap also installs another package? For example, wget. Thanks.






      apt package-management snap deb packaging







      share|improve this question














      Can a snap be built in a way such as, when the user tries to install it, the snap also installs another package? For example, wget. Thanks.






      apt package-management snap deb packaging




      apt package-management snap deb packaging






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 2 days ago









      knocteknocte

      689820




      689820






















          2 Answers
          2






          active

          oldest

          votes


















          1














          The short answer to your question is: no, snaps cannot depend upon .debs in such as way that, when the snap is installed, the .deb is installed as well.



          However, the longer answer is that, when building the snap, you can bundle whatever .debs you want within it. To use your example, here's the snapcraft.yaml for a snap that bundles wget within it:



          name: my-snap-name # you probably want to 'snapcraft register <name>'
          
base: core18 # the base snap is the execution environment for this snap
          
version: '0.1' # just for humans, typically '1.2+git' or '1.3.2'
          
summary: Single-line elevator pitch for your amazing snap # 79 char long summary
          
description: |
          
  This is my-snap's description. You have a paragraph or two to tell the
          
  most important story about your snap. Keep it under 100 words though,
          
  we live in tweetspace and your description wants to look good in the snap
          
  store.
          

          
grade: devel # must be 'stable' to release into candidate/stable channels
          
confinement: strict # 'strict' confinement means fully confined
          

          
parts: 
          
  my-part:
          
    plugin: nil
          
    # Include the wget .deb from the Ubuntu package archive
          
    stage-packages: [wget]
          

          
apps:
          
  # expose wget to end-users
          
  wget:
          
    command: usr/bin/wget
          
    plugs: [network, home, removable-media]


          Run snapcraft on that and you end up with a snap that has a wget app. It doesn't pull wget in at install-time like you asked, but by pulling it in at build-time perhaps it accomplishes your end goal.






          share|improve this answer
























          • thanks! this is for a binary, but what if I also need libs from usr/lib?

            – knocte
            2 days ago











          • for example: gtk2 libs?

            – knocte
            2 days ago











          • Same thing, just add it to stage-packages and they'll end up in the snap.

            – Kyle
            yesterday



















          0














          Snap packages are self contained and need no outside dependencies to run.
          See here for more information Linux Commando: Snaps






          share|improve this answer
























          • that guide is only written from the user point of view, not from the developer that wants to create the snap; I mean, I know that a snap can be self contained and include all dependencies inside, but if a .deb package already provides a version that is compatible with the app contained in the snap, and the snap builder decides it's good enough, can the snap depend on the .deb?

            – knocte
            2 days ago






          • 2





            that may be true but the whole Idea of the snap is that it will work across many distros so if the developer require a dependency outside the snap that may not be the case because different distros may place files in different locations. JMHO.

            – kc1di
            2 days ago






          • 1





            A snap that depends upon a deb is non-portable, can be confusing to some users, and adds an unnecessary support burden to the developer. A more immediate problem is that snaps have no way to communicate a deb dependency to apt. This makes the install non-standard, and another pain point for support: We all know that humans sometimes aren't great at following simple directions.

            – user535733
            2 days ago













          • This conical guide should answer your question more throughly : docs.snapcraft.io/the-snap-format/698

            – kc1di
            2 days ago











          • @user535733: ok even if it's non-portable, I'm aware of the disadvantage of this, how can I do it?

            – knocte
            2 days ago











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "89"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1113031%2fcan-a-snap-package-depend-on-a-deb-package-provided-by-the-distro%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1














          The short answer to your question is: no, snaps cannot depend upon .debs in such as way that, when the snap is installed, the .deb is installed as well.



          However, the longer answer is that, when building the snap, you can bundle whatever .debs you want within it. To use your example, here's the snapcraft.yaml for a snap that bundles wget within it:



          name: my-snap-name # you probably want to 'snapcraft register <name>'
          
base: core18 # the base snap is the execution environment for this snap
          
version: '0.1' # just for humans, typically '1.2+git' or '1.3.2'
          
summary: Single-line elevator pitch for your amazing snap # 79 char long summary
          
description: |
          
  This is my-snap's description. You have a paragraph or two to tell the
          
  most important story about your snap. Keep it under 100 words though,
          
  we live in tweetspace and your description wants to look good in the snap
          
  store.
          

          
grade: devel # must be 'stable' to release into candidate/stable channels
          
confinement: strict # 'strict' confinement means fully confined
          

          
parts: 
          
  my-part:
          
    plugin: nil
          
    # Include the wget .deb from the Ubuntu package archive
          
    stage-packages: [wget]
          

          
apps:
          
  # expose wget to end-users
          
  wget:
          
    command: usr/bin/wget
          
    plugs: [network, home, removable-media]


          Run snapcraft on that and you end up with a snap that has a wget app. It doesn't pull wget in at install-time like you asked, but by pulling it in at build-time perhaps it accomplishes your end goal.






          share|improve this answer
























          • thanks! this is for a binary, but what if I also need libs from usr/lib?

            – knocte
            2 days ago











          • for example: gtk2 libs?

            – knocte
            2 days ago











          • Same thing, just add it to stage-packages and they'll end up in the snap.

            – Kyle
            yesterday
















          1














          The short answer to your question is: no, snaps cannot depend upon .debs in such as way that, when the snap is installed, the .deb is installed as well.



          However, the longer answer is that, when building the snap, you can bundle whatever .debs you want within it. To use your example, here's the snapcraft.yaml for a snap that bundles wget within it:



          name: my-snap-name # you probably want to 'snapcraft register <name>'
          
base: core18 # the base snap is the execution environment for this snap
          
version: '0.1' # just for humans, typically '1.2+git' or '1.3.2'
          
summary: Single-line elevator pitch for your amazing snap # 79 char long summary
          
description: |
          
  This is my-snap's description. You have a paragraph or two to tell the
          
  most important story about your snap. Keep it under 100 words though,
          
  we live in tweetspace and your description wants to look good in the snap
          
  store.
          

          
grade: devel # must be 'stable' to release into candidate/stable channels
          
confinement: strict # 'strict' confinement means fully confined
          

          
parts: 
          
  my-part:
          
    plugin: nil
          
    # Include the wget .deb from the Ubuntu package archive
          
    stage-packages: [wget]
          

          
apps:
          
  # expose wget to end-users
          
  wget:
          
    command: usr/bin/wget
          
    plugs: [network, home, removable-media]


          Run snapcraft on that and you end up with a snap that has a wget app. It doesn't pull wget in at install-time like you asked, but by pulling it in at build-time perhaps it accomplishes your end goal.






          share|improve this answer
























          • thanks! this is for a binary, but what if I also need libs from usr/lib?

            – knocte
            2 days ago











          • for example: gtk2 libs?

            – knocte
            2 days ago











          • Same thing, just add it to stage-packages and they'll end up in the snap.

            – Kyle
            yesterday














          1












          1








          1







          The short answer to your question is: no, snaps cannot depend upon .debs in such as way that, when the snap is installed, the .deb is installed as well.



          However, the longer answer is that, when building the snap, you can bundle whatever .debs you want within it. To use your example, here's the snapcraft.yaml for a snap that bundles wget within it:



          name: my-snap-name # you probably want to 'snapcraft register <name>'
          
base: core18 # the base snap is the execution environment for this snap
          
version: '0.1' # just for humans, typically '1.2+git' or '1.3.2'
          
summary: Single-line elevator pitch for your amazing snap # 79 char long summary
          
description: |
          
  This is my-snap's description. You have a paragraph or two to tell the
          
  most important story about your snap. Keep it under 100 words though,
          
  we live in tweetspace and your description wants to look good in the snap
          
  store.
          

          
grade: devel # must be 'stable' to release into candidate/stable channels
          
confinement: strict # 'strict' confinement means fully confined
          

          
parts: 
          
  my-part:
          
    plugin: nil
          
    # Include the wget .deb from the Ubuntu package archive
          
    stage-packages: [wget]
          

          
apps:
          
  # expose wget to end-users
          
  wget:
          
    command: usr/bin/wget
          
    plugs: [network, home, removable-media]


          Run snapcraft on that and you end up with a snap that has a wget app. It doesn't pull wget in at install-time like you asked, but by pulling it in at build-time perhaps it accomplishes your end goal.






          share|improve this answer













          The short answer to your question is: no, snaps cannot depend upon .debs in such as way that, when the snap is installed, the .deb is installed as well.



          However, the longer answer is that, when building the snap, you can bundle whatever .debs you want within it. To use your example, here's the snapcraft.yaml for a snap that bundles wget within it:



          name: my-snap-name # you probably want to 'snapcraft register <name>'
          
base: core18 # the base snap is the execution environment for this snap
          
version: '0.1' # just for humans, typically '1.2+git' or '1.3.2'
          
summary: Single-line elevator pitch for your amazing snap # 79 char long summary
          
description: |
          
  This is my-snap's description. You have a paragraph or two to tell the
          
  most important story about your snap. Keep it under 100 words though,
          
  we live in tweetspace and your description wants to look good in the snap
          
  store.
          

          
grade: devel # must be 'stable' to release into candidate/stable channels
          
confinement: strict # 'strict' confinement means fully confined
          

          
parts: 
          
  my-part:
          
    plugin: nil
          
    # Include the wget .deb from the Ubuntu package archive
          
    stage-packages: [wget]
          

          
apps:
          
  # expose wget to end-users
          
  wget:
          
    command: usr/bin/wget
          
    plugs: [network, home, removable-media]


          Run snapcraft on that and you end up with a snap that has a wget app. It doesn't pull wget in at install-time like you asked, but by pulling it in at build-time perhaps it accomplishes your end goal.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 2 days ago









          KyleKyle

          4,2071319




          4,2071319













          • thanks! this is for a binary, but what if I also need libs from usr/lib?

            – knocte
            2 days ago











          • for example: gtk2 libs?

            – knocte
            2 days ago











          • Same thing, just add it to stage-packages and they'll end up in the snap.

            – Kyle
            yesterday



















          • thanks! this is for a binary, but what if I also need libs from usr/lib?

            – knocte
            2 days ago











          • for example: gtk2 libs?

            – knocte
            2 days ago











          • Same thing, just add it to stage-packages and they'll end up in the snap.

            – Kyle
            yesterday

















          thanks! this is for a binary, but what if I also need libs from usr/lib?

          – knocte
          2 days ago





          thanks! this is for a binary, but what if I also need libs from usr/lib?

          – knocte
          2 days ago













          for example: gtk2 libs?

          – knocte
          2 days ago





          for example: gtk2 libs?

          – knocte
          2 days ago













          Same thing, just add it to stage-packages and they'll end up in the snap.

          – Kyle
          yesterday





          Same thing, just add it to stage-packages and they'll end up in the snap.

          – Kyle
          yesterday













          0














          Snap packages are self contained and need no outside dependencies to run.
          See here for more information Linux Commando: Snaps






          share|improve this answer
























          • that guide is only written from the user point of view, not from the developer that wants to create the snap; I mean, I know that a snap can be self contained and include all dependencies inside, but if a .deb package already provides a version that is compatible with the app contained in the snap, and the snap builder decides it's good enough, can the snap depend on the .deb?

            – knocte
            2 days ago






          • 2





            that may be true but the whole Idea of the snap is that it will work across many distros so if the developer require a dependency outside the snap that may not be the case because different distros may place files in different locations. JMHO.

            – kc1di
            2 days ago






          • 1





            A snap that depends upon a deb is non-portable, can be confusing to some users, and adds an unnecessary support burden to the developer. A more immediate problem is that snaps have no way to communicate a deb dependency to apt. This makes the install non-standard, and another pain point for support: We all know that humans sometimes aren't great at following simple directions.

            – user535733
            2 days ago













          • This conical guide should answer your question more throughly : docs.snapcraft.io/the-snap-format/698

            – kc1di
            2 days ago











          • @user535733: ok even if it's non-portable, I'm aware of the disadvantage of this, how can I do it?

            – knocte
            2 days ago
















          0














          Snap packages are self contained and need no outside dependencies to run.
          See here for more information Linux Commando: Snaps






          share|improve this answer
























          • that guide is only written from the user point of view, not from the developer that wants to create the snap; I mean, I know that a snap can be self contained and include all dependencies inside, but if a .deb package already provides a version that is compatible with the app contained in the snap, and the snap builder decides it's good enough, can the snap depend on the .deb?

            – knocte
            2 days ago






          • 2





            that may be true but the whole Idea of the snap is that it will work across many distros so if the developer require a dependency outside the snap that may not be the case because different distros may place files in different locations. JMHO.

            – kc1di
            2 days ago






          • 1





            A snap that depends upon a deb is non-portable, can be confusing to some users, and adds an unnecessary support burden to the developer. A more immediate problem is that snaps have no way to communicate a deb dependency to apt. This makes the install non-standard, and another pain point for support: We all know that humans sometimes aren't great at following simple directions.

            – user535733
            2 days ago













          • This conical guide should answer your question more throughly : docs.snapcraft.io/the-snap-format/698

            – kc1di
            2 days ago











          • @user535733: ok even if it's non-portable, I'm aware of the disadvantage of this, how can I do it?

            – knocte
            2 days ago














          0












          0








          0







          Snap packages are self contained and need no outside dependencies to run.
          See here for more information Linux Commando: Snaps






          share|improve this answer













          Snap packages are self contained and need no outside dependencies to run.
          See here for more information Linux Commando: Snaps







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 2 days ago









          kc1dikc1di

          744




          744













          • that guide is only written from the user point of view, not from the developer that wants to create the snap; I mean, I know that a snap can be self contained and include all dependencies inside, but if a .deb package already provides a version that is compatible with the app contained in the snap, and the snap builder decides it's good enough, can the snap depend on the .deb?

            – knocte
            2 days ago






          • 2





            that may be true but the whole Idea of the snap is that it will work across many distros so if the developer require a dependency outside the snap that may not be the case because different distros may place files in different locations. JMHO.

            – kc1di
            2 days ago






          • 1





            A snap that depends upon a deb is non-portable, can be confusing to some users, and adds an unnecessary support burden to the developer. A more immediate problem is that snaps have no way to communicate a deb dependency to apt. This makes the install non-standard, and another pain point for support: We all know that humans sometimes aren't great at following simple directions.

            – user535733
            2 days ago













          • This conical guide should answer your question more throughly : docs.snapcraft.io/the-snap-format/698

            – kc1di
            2 days ago











          • @user535733: ok even if it's non-portable, I'm aware of the disadvantage of this, how can I do it?

            – knocte
            2 days ago



















          • that guide is only written from the user point of view, not from the developer that wants to create the snap; I mean, I know that a snap can be self contained and include all dependencies inside, but if a .deb package already provides a version that is compatible with the app contained in the snap, and the snap builder decides it's good enough, can the snap depend on the .deb?

            – knocte
            2 days ago






          • 2





            that may be true but the whole Idea of the snap is that it will work across many distros so if the developer require a dependency outside the snap that may not be the case because different distros may place files in different locations. JMHO.

            – kc1di
            2 days ago






          • 1





            A snap that depends upon a deb is non-portable, can be confusing to some users, and adds an unnecessary support burden to the developer. A more immediate problem is that snaps have no way to communicate a deb dependency to apt. This makes the install non-standard, and another pain point for support: We all know that humans sometimes aren't great at following simple directions.

            – user535733
            2 days ago













          • This conical guide should answer your question more throughly : docs.snapcraft.io/the-snap-format/698

            – kc1di
            2 days ago











          • @user535733: ok even if it's non-portable, I'm aware of the disadvantage of this, how can I do it?

            – knocte
            2 days ago

















          that guide is only written from the user point of view, not from the developer that wants to create the snap; I mean, I know that a snap can be self contained and include all dependencies inside, but if a .deb package already provides a version that is compatible with the app contained in the snap, and the snap builder decides it's good enough, can the snap depend on the .deb?

          – knocte
          2 days ago





          that guide is only written from the user point of view, not from the developer that wants to create the snap; I mean, I know that a snap can be self contained and include all dependencies inside, but if a .deb package already provides a version that is compatible with the app contained in the snap, and the snap builder decides it's good enough, can the snap depend on the .deb?

          – knocte
          2 days ago




          2




          2





          that may be true but the whole Idea of the snap is that it will work across many distros so if the developer require a dependency outside the snap that may not be the case because different distros may place files in different locations. JMHO.

          – kc1di
          2 days ago





          that may be true but the whole Idea of the snap is that it will work across many distros so if the developer require a dependency outside the snap that may not be the case because different distros may place files in different locations. JMHO.

          – kc1di
          2 days ago




          1




          1





          A snap that depends upon a deb is non-portable, can be confusing to some users, and adds an unnecessary support burden to the developer. A more immediate problem is that snaps have no way to communicate a deb dependency to apt. This makes the install non-standard, and another pain point for support: We all know that humans sometimes aren't great at following simple directions.

          – user535733
          2 days ago







          A snap that depends upon a deb is non-portable, can be confusing to some users, and adds an unnecessary support burden to the developer. A more immediate problem is that snaps have no way to communicate a deb dependency to apt. This makes the install non-standard, and another pain point for support: We all know that humans sometimes aren't great at following simple directions.

          – user535733
          2 days ago















          This conical guide should answer your question more throughly : docs.snapcraft.io/the-snap-format/698

          – kc1di
          2 days ago





          This conical guide should answer your question more throughly : docs.snapcraft.io/the-snap-format/698

          – kc1di
          2 days ago













          @user535733: ok even if it's non-portable, I'm aware of the disadvantage of this, how can I do it?

          – knocte
          2 days ago





          @user535733: ok even if it's non-portable, I'm aware of the disadvantage of this, how can I do it?

          – knocte
          2 days ago


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Ask Ubuntu!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid …



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1113031%2fcan-a-snap-package-depend-on-a-deb-package-provided-by-the-distro%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          -

          Popular posts from this blog

          數位音樂下載

          Image
          數位音樂下載 為非以「實體」方式來販賣音樂的相關產品，而使用數位格式如mp3、AAC等文件格式來進行銷售販賣的一种音乐产业形式。著名的數位音樂下載服務商有iTunes Store、RecoChoku、Google Play音乐和微软Zune等。数字音乐下载在二十一世纪初一度风靡全球， [1] [2] 使得传统唱片产业走向衰落，但其自身也在2010年代流媒体音乐服务如Apple Music、Spotify等的挤压下迅速失去市场份额。 [3] [4] 数字音乐下载有便于携带、传播迅速、制作简单成本低等优点，与流媒体音乐相比也能更好保障音乐人权益； [5] 但它同时很可能带来侵犯版权和滥用的情形， [6] 也给音乐产业带来了诸多不利影响。数字音乐下载为音乐人和乐迷提供了更加便捷直接的交流渠道，也一定程度上推动了网络音乐人的出现和独立音乐的迅速发展。 [7] 目录 1 历史 1.1 技术积淀（1987-2000） 1.2 出现与兴起（2000-2004） 1.3 唱片市场的颠覆者（2004-2007） 1.4 巅峰和衰落（2005-2013） 1.5 摇摇欲坠的现状与不可预知的明天（2014至今） 2 主要文件格式 2.1 PCM编码格式 2.1.1 WAV 2.1.2 APE 2.1.3 FLAC 2.2 苹果推出的无损文件格式 2.2.1 AIFF 2.2.2 ALAC 2.3 有损压缩格式 2.3.1 MP3 2.3.2 AAC 3 主要市场 3.1 iTunes Store 3.2 Google Play音乐商店 3.3 亚马逊音乐商店 3.4 部分其他音乐商店 4 影响与评价 4.1 对音乐产业的影响 4.2 对科技行业的影响 4.3 正面评价 4.4 负面评价 4.4.1 侵权问题 4.4.2 经营模式不明晰 4.4.3 不适应移动时代 4.5 文化现象 5 延伸阅读 6 参考资料 历史 苹果iTunes+iPod的软硬件搭配让数字音...
          Read more

          When can things happen in Etherscan, such as the picture below?

          Image
          2 I don't know why balance of the address is 0. when can this situation? etherscan balances share | improve this question asked yesterday Ru Hi Ru Hi 11 1 New contributor Ru Hi is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct. add a comment  |  ...
          Read more

          格利澤436b

          Image
          格利泽436b 太陽系外行星 太陽系外行星列表 艺术家笔下的格利泽436b 母恆星 母恆星 Gliese 436 星座 獅子座 赤經 ( α ) 11 h  42 m  11.0941 s [1] 赤緯 ( δ ) +26° 42′ 23.652″ [1] 距離 33.4 ly (10.2 pc) 光譜類型 M2.5 V [1] 軌道參數 半长轴 ( a ) 0.0291±0.0004 [2] AU 軌道離心率 ( e ) 0.150±0.012 [2] 公轉週期 ( P ) 2.643904±0.000005 [3] d (0.00723849 y) 軌道傾角 ( i ) 85.8 +0.21 −0.25 [3] ° 角距 ( θ ) 2.794 mas 近星點時間 ( T 0 ) 2,451,551.716 ±0.01 JD 半振幅 ( K ) 18.68±0.8 m/s 物理性质 质量 ( m ) 22.2±1.0 [2] M ⊕ 半徑 ( r ) 4.327±0.183 [2] [4] R ⊕ 密度 ( ρ ) 1.51 g cm -3 表面重力 ( g ) 1.18 g 溫度 ( T ) 712±36 [2] K 發現 發現時間 2004 發現者 巴特勒、沃格特、 馬西 et al. 發現方法 徑向速度、凌日法 發現地點 美國加利福尼亞州 發表論文 出版 其他名稱 Ross 905 b, GJ 436 b, [5] LTT 13213 b, GCTP 2704.10 b, LHS 310, AC+27:28217 b, Vyssotsky 616 b, HIP 57087 b, GEN# +9.80120068 b, LP 319-75 b, G 121-7 b, LSPM J1142+2642 b, 1RXS J114211.9+264328 b, ASCC 683818 b, G 147-68 b, UCAC2 41198281 b, BP...
          Read more