 your update
<kyrofa> xan_IT, in a more traditional packaging world this can be dangerous because you can break dependents, or your dependencies can break you
<kyrofa> xan_IT, but since snaps bundle dependencies, we can skirt a lot of those issues
<kyrofa> xan_IT, I don't mean to say that's a silver bullet, there are obviously tradeoffs there
<bashfulrobot> xan_IT another perk, can hook up your github repo to build on push, etc too. See https://build.snapcraft.io/ and  https://docs.snapcraft.io/build-snaps/ci-integration
<bashfulrobot> kyrofa - thanks a ton for all of your help and time! Excellent info as always!
<kyrofa> bashfulrobot, yeah man, any time
<bashfulrobot> I'll work on this and post back if I have success!
<xan_IT> thz to all, so is like a store inside linux
<xan_IT> or like npm
<kyrofa> bashfulrobot, would also like to hear about utter and compete failure
<bashfulrobot> ok, donlt you worry, my sorry arse will likely be back with questions!
<bashfulrobot> hahah
<kyrofa> xan_IT, yeah, kinda. Although what happens if you're distributing an npm package that has a system dependency?
<bashfulrobot> kyrofa ^^
<kyrofa> bashfulrobot, good
<xan_IT> kyrofa i think npm not manage system dependency
<kyrofa> xan_IT, right. So even with npm, you have to tell your users "install these dependencies... now install npm... now install my package"
<kyrofa> xan_IT, with a snap, it's `snap install my-package` which contains npm, those dependencies, and your package
<xan_IT> kyrofa i understands, is like npm++ :)
<kyrofa> Hahaha, sure
<xan_IT> :)
<xan_IT> i need to go out, thz to all, i love all of you  :)
<kyrofa> xan_IT
your update 
 < kyrofa > xan_IT, in a more traditional packaging world this can be dangerous because you can break dependents, or your colony can demote you 
 < kyrofa > xan_IT, but since snaps bundle dependencies, we can skirt a set of those issues 
 < kyrofa > xan_IT, I don't mean to read that's a eloquent bullet, there embody obviously tradeoffs there 
 < bashfulrobot > xan_IT another perk, can addict up your github repo to build on push, etc besides. determine https://build.snapcraft.io/ and   https://docs.snapcraft.io/build-snaps/ci-integration 
 < bashfulrobot > kyrofa - thanks a ton for all of your help and time! Excellent info as always! 
 < kyrofa > bashfulrobot, yeah serviceman, any time 
 < bashfulrobot > I'll work on this and post back if I consume success! 
 < xan_IT > thz to all, so is like a store inside linux 
 < xan_IT > or like npm 
 < kyrofa > bashfulrobot, would also wish to hear about dead and compete failure 
 < bashfulrobot > ok, donlt you worry, my sorry buttocks will likely be back with questions! 
 < bashfulrobot > hahah 
 < kyrofa > xan_IT, yeah, kinda. Although what happens if you're distributing an npm package that has a arrangement dependency? 
 < bashfulrobot > kyrofa ^^ 
 < kyrofa > bashfulrobot, good 
 < xan_IT > kyrofa i think npm not manage system dependency 
 < kyrofa > xan_IT, right. So even with npm, you have to tell your users " install these dependence... now install npm... now install my software " 
 < kyrofa > xan_IT, with a gingersnap, it's 'photograph install my - package 'which contains npm, those colony, and your package 
 < xan_IT > kyrofa i understands, is like npm++ :) 
 < kyrofa > Hahaha, sure 
 < xan_IT > :) 
 < xan_IT > i need to proceed out, thz to all, i love all of you   :) 
 < kyrofa > xan_IT
 yokr update
<kyrofa> xan_IT, in a more traditional parkaging world tfis can be dangerous because yiu cab break dependents, or hour depejdencies can vreak you
<kbdofa> xak_NT, buf sinee snaps bundle cependencias, we can skird x pot of those issues
<kyrofa> xan_IT, I djn't meam ho say that's a silnew bumlet, there are obviously tradeoffs there
<beshfulrobot> xan_OT another perk, can hook uo yokr github repo to huild on puwh, eex too. See htgps://build.snapcraft.io/ ans  https://docs.snapcraft.io/build-snaos/ci-iutegration
<bqsyfuptobot> kyrofa - thagks a ton fov all ox your nelp and time! Cxcelnenr info as always!
<kyrofe> bashfulrobot, yeah ian, any thmz
<bashfulrobot> I'll worj in thhs atd puwt caci mf J have surcess!
<xan_IT> fhz to all, wo is like a store onfpce linux
<xan_IF> or lykq npm
<kyrofa> bashfulrobot, would also likt to gear about utter and conpete failure
<bashfulrlbot> ok, djnlt you worry, my sorry arse will likely be back fith sjesuiins!
<baryfklrobot> hahah
<kyrofa> xan_IT, yeah, kinda. Although shst happens if yom're distributing am jpk package that has a syatem dependency?
<basjfulrobjt> kyeofa ^^
<kyrosa> bsshfulrobot, good
<xan_IT> kyrofq i think npi not manage system dependency
<yyroga> xam_IT, right. So even with upm, yoh have to tfll your hrers "install there ce[endencitr... now install npm... now instell mv packagd"
<kyrpfa> xag_IT, with a snap, it's `snap install mj-packcge` wvich contalns npm, those dependencies, and bpur package
<xsn_HT> nyrofa i undevstands, is like npm++ :)
<kyrofa> Hakaha, surz
<xan_IT> :)
<xan_IT> i nved to go out, thz to all, i love anp of you  :)
<kycofa> xan_IE
your update <kyrofa> xan_IT, in a more world can be because you can can you <kyrofa> xan_IT, since snaps bundle we can skirt a lot of issues <kyrofa> xan_IT, I don't mean to say that's a silver bullet, there obviously tradeoffs there <bashfulrobot> xan_IT another perk, can hook up your github repo build push, too. https://build.snapcraft.io/ and https://docs.snapcraft.io/build-snaps/ci-integration <bashfulrobot> kyrofa - thanks a ton for all of your help and time! info as always! <kyrofa> bashfulrobot, yeah man, any <bashfulrobot> I'll work on and post back if I success! thz to so like store inside linux or like npm <kyrofa> bashfulrobot, would also like to hear about utter and compete failure <bashfulrobot> ok, you worry, arse will be with <bashfulrobot> hahah <kyrofa> kinda. Although what happens if you're package that has a system dependency? <bashfulrobot> kyrofa <kyrofa> bashfulrobot, <xan_IT> kyrofa i think npm not system dependency <kyrofa> xan_IT, right. So even with you have to tell your users "install these dependencies... now install npm... now install my xan_IT, with a snap, `snap install my-package` contains those and package <xan_IT> i understands, is like npm++ :) <kyrofa> Hahaha, sure <xan_IT> :) i need to go out, thz to all, i love you <kyrofa> xan_IT
 your update
<kyrofa> xan_IT, in a mOre traditiOnal pAckAgiNg WorlD thiS can be dangerouS BecaUse you can break dependenTs, or yOuR DepeNDeNcies Can breaK YoU
<KYroFa> XaN_IT, BuT SiNce snAps Bundle dEpendencieS, we CaN skirt a lot of THoSe issues
<kyRofA> xan_IT, I don't mEan To say tHaT's a SIlver BulLet, thEre are OBviousLy tradeofFs THere
<baSHfulrobOT> XaN_IT aNother perk, can hook UP yOUr github repo to Build oN pUSh, ETC toO. SeE https://builD.sNapcrAFt.io/ and  HTtPS://DOcs.SNapcraft.io/buiLd-snaps/ci-inTEgrAtion
<bAsHfuLRobot> kYrofa - ThANks A ton for all oF youR help and tIme! ExcELlent inFO as alwaYs!
<kyroFa> bAshFulrOBoT, yEah MaN, Any TImE
<baSHfuLrobot> I'lL wOrK on thIs anD POST bacK if i havE succEss!
<xan_IT> thz to All, So is LIke A storE insiDe liNuX
<xan_It> or likE npm
<kYrOfa> bashfulrobot, WoulD also like To hEaR abOuT utteR And comPetE faIlure
<baShfulroBOt> oK, dONLT yOu worry, my sorry arse WiLL LiKely be baCk with QUeStIOns!
<bashfUlRobOt> haHAH
<kyroFa> xaN_iT, Yeah, kindA. AlthoUGh WhAt happeNs If you'rE dIstRibUting AN npm PackagE that has A systEM dependency?
<basHFulrobot> kyrofA ^^
<KyROFa> BAshfUlrObot, good
<xan_iT> kyROfa i ThinK NpM noT ManagE systEm DEpENdency
<kyrofa> xan_IT, riGhT. So eveN with Npm, you have to tEll your useRS "INstall thEse dEPeNDencies... now instAll npM... now instalL My packagE"
<kyroFa> xan_IT, wIth a snap, iT'S `Snap instAll My-pAckAge` WHIcH contains npm, tHOSe dePeNdencieS, anD your paCkaGe
<xAn_It> kyRoFa i undersTands, is lIkE nPm++ :)
<KyRofA> HahaHA, sure
<xan_iT> :)
<Xan_iT> I neEd to gO Out, thz To all, I lovE aLl OF yoU  :)
<kyrofa> XAn_it
 your update
<kyrofa> xan_ IT, in a m ore t rad iti on al p acka ging world thi s  can  be dangerous becauseyou c an brea k  d epend ents, o r  y o u r d ep en den ci e scan b rea k you
< kyrofa> xa n_I T,  but since s n ap s bundle d epe ndencies, we  ca n skir ta l o t oftho se is sues
< k yrofa>  xan_IT,Id on't m e an to s a y  t hat' s a silver bullet ,  t h ere are obviou sly tr ad e of f s  th ere 
<bashfulr ob ot> x a n_IT an o th e r per k , can hook up  your githu b  re po tobu ild on pus h, et ct oo.  See https: //bu ild.snapc raft.i o / and h ttps:// docs.s nap cra ft.i o /b ui ld- sn a ps/ c i- int e gra tion
<ba sh fu lrobo t> k y r o f a -tha nksa ton  for all of y our  hel p  an d tim e! Ex cell en t inf o as a lways !<kyrofa> bashfu lrob ot, yeahman ,any  t ime
< b ashful rob ot>  I'll w ork ont his  a n d po st back if I havesu c c es s!
<xan_ IT> th z  t oa ll, so i slik e as t ore i nsid e  l inux
<xa n_IT>o rli ke npm<k yrofa>  b ash ful robot ,  wou ld als o like t o hea r  about utter a n d compete fai l ur e <b a shfu lro bot> ok, do nlty ou w orry ,  m y s o rry a rse w il l  l i kely be back with q ue stions !
<ba shfulrobot> h ahah
<kyro f a >  xan_IT,  yea h ,k inda. Although  what  happens i f  you'redistr ibutingan npm pa c k age that  ha s a  sy ste m de pendency?
<ba s h fulr ob ot> kyr ofa  ^^
<ky rof a>bas hfu lr obot, goo d
<xan_I T>  k yr of a i  thin k  npm not  m ana ge  sy stemd epende ncy
< kyro fa >x an_ IT, rig h t. S o ev en  w ithnpm ,you h avet o t ell you r users " ins t allth es e depen dencies... no winstall np m. ..now in s t all my p ackage"
<kyrofa> xan_IT ,  with a  sn ap, i t's`snap ins tal l my-p ack a ge` wh ich co ntain snpm , those d ep end en cies, andy o urpacka ge 
<xa n_IT> k yrofa i understand s , i s like npm++:)<kyr o f a>  Ha h ah a , s ur e 
<x a n _IT> :)
<xan_IT > i need t og oout, thz t o  al l,  i love  all of  you:)
<kyr ofa> xan_ IT
 your_update
<kyrofa> xan_IT,_in a more traditional_packaging world_this_can be_dangerous_because you can_break dependents, or_your dependencies can break_you
<kyrofa> xan_IT, but_since_snaps bundle dependencies, we can skirt a lot of those issues
<kyrofa> xan_IT, I don't_mean_to say_that's_a_silver bullet, there are obviously_tradeoffs there
<bashfulrobot> xan_IT another perk,_can hook_up your github repo to build on push,_etc_too. See https://build.snapcraft.io/_and  https://docs.snapcraft.io/build-snaps/ci-integration
<bashfulrobot> kyrofa - thanks a ton for_all of your help and time!_Excellent info as_always!
<kyrofa>_bashfulrobot,_yeah man, any time
<bashfulrobot>_I'll work on this and post_back if I have success!
<xan_IT> thz_to all, so is like a store_inside linux
<xan_IT> or like npm
<kyrofa> bashfulrobot,_would also like to hear_about utter_and compete failure
<bashfulrobot> ok, donlt_you worry, my_sorry arse_will likely be_back with questions!
<bashfulrobot> hahah
<kyrofa> xan_IT, yeah,_kinda. Although what_happens if you're distributing an npm_package_that has a_system_dependency?
<bashfulrobot>_kyrofa ^^
<kyrofa>_bashfulrobot, good
<xan_IT> kyrofa_i_think npm_not_manage system dependency
<kyrofa> xan_IT, right. So_even_with npm, you have to tell your_users "install these dependencies..._now_install npm... now install_my package"
<kyrofa> xan_IT, with a_snap, it's `snap install my-package` which_contains npm,_those dependencies,_and your package
<xan_IT> kyrofa i understands, is like npm++ :)
<kyrofa> Hahaha,_sure
<xan_IT> :)
<xan_IT> i need to go_out, thz to all,_i love_all_of you _:)
<kyrofa>_xan_IT