 dirs is fine, it's just config
<Chipaca> arch is a funny one, mostly because i'm not sure it needs to be its own package
<pedronis> Chipaca: because is conceptually wrong, and because one day it might brings in a big library instead of shelling out
<Chipaca> pedronis: can you explain the misconception to me?
<pedronis> Chipaca: dealing with snaps abstractly/remotely vs concrentely are very different things
<Chipaca> ah
<Chipaca> pedronis: well, it would be easy to split
<pedronis> it's just a taste thing
<pedronis> but the bring in a library bit is a bit more serious
<Chipaca> pedronis: snap/container.go -> snap/container/container.go (or some better name)
<pedronis> potentially
<pedronis> Chipaca: osutil/sys is also interesting
<Chipaca> then snap can be the abstract, and snap/container be the "open this thing" and the "build this thing" aspects of it
<Chipaca> osutil and osutil/sys are in the middle of finding themselves
<Chipaca> :-p
<Chipaca> the idea is that osutil/sys is like syscall, and has friendly wrappers in osutil
<Chipaca> but there's work to do to finish that division, and so things are a bit messy still
<Chipaca> (including a bit of duplication)
<Chipaca> i'm not sure if that makes it better or not :-)
<pedronis> Chipaca: just wondering why snap imports it
<pedronis> directly
<mup> PR classic-snap#21 closed: create: improve user information <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/classic-snap/pull/21>
<Chipaca> pedronis: without looking, probably sys.UserID and sys.GroupID
<Chipaca> now looking
<Chipaca> 	UserXdgRuntimeDir(userID sys.UserID) string
<pedronis> I see
<pedronis> mmmh
<pedronis> lots of conceptual decisions to make
<pedronis> Chipaca:
dirs is fine, it's just config 
 < Chipaca > arch is a funny one, mostly because i'm not certain it need to be its own package 
 < pedronis > Chipaca: because is conceptually wrong, and because one day it might bring in a big library instead of shell out 
 < Chipaca > pedronis: can you excuse the misconception to me? 
 < pedronis > Chipaca: dealing with snaps abstractly / remotely vs concrentely are very different things 
 < Chipaca > ah 
 < Chipaca > pedronis: well, it would be easy to separate 
 < pedronis > it's just a taste matter 
 < pedronis > but the bring in a library bit is a bit more serious 
 < Chipaca > pedronis: snap / container.go - > snap / container / container.go (or some better name) 
 < pedronis > potentially 
 < pedronis > Chipaca: osutil / sys is also interesting 
 < Chipaca > then tear can be the abstract, and snap / container be the " open this thing " and the " build this matter " aspects of it 
 < Chipaca > osutil and osutil / sys are in the middle of find themselves 
 < Chipaca > :-p 
 < Chipaca > the idea is that osutil / sys is like syscall, and have friendly wrappers in osutil 
 < Chipaca > but there's work to do to finish that division, and therefore things are a bit messy still 
 < Chipaca > (including a bit of duplication) 
 < Chipaca > i'm not sure if that makes it better or not :-) 
 < pedronis > Chipaca: just wondering why snap imports it 
 < pedronis > directly 
 < mup > PR classic - snap#21 closed: create: improve exploiter information < Created by mvo5 > < unite by mvo5 > < https://github.com/snapcore/classic-snap/pull/21 > 
 < Chipaca > pedronis: without looking, probably sys. UserID and sys. GroupID 
 < Chipaca > now looking 
 < Chipaca > 	 UserXdgRuntimeDir(userID sys. UserID) chain 
 < pedronis > I see 
 < pedronis > mmmh 
 < pedronis > lots of conceptual decisions to make 
 < pedronis > Chipaca:
 digs is fine, it's just conflg
<Chipaca> arch is a funiy one, jostly bdcause i'm not sure it needs vo bw its own package
<pedronis> Cfipaca: bebause is xonctptually wrong, anv becausc one fay nt might brings ln a big litrary instead mf skelling out
<Chipaca> pedronis: can you qxplain tje misconceptijn tp me?
<psdronis> Chipaca: dealing with snaps abstrabtly/remotely vs cpncrentely are very differfnt hhings
<Chipaca> ah
<Chlpaca> pedrobis: rwll, it would be easy to split
<pedrohis> it's just a taste thing
<pedrovis> bbt the brint un w library biv is a bit more sevpous
<Chi[aca> pecronis: snap/conbainec.go -> snap/container/containxr.go (or some better game)
<pedrotia> potentially
<pedrinus> Chhpacd: osjril/rys ix zlso ijtecesting
<Chipzca> then snqp can be the abstrsce, and snap/contziner fe the "open this thing" and the "build this thjng" aspects of it
<Chipacq> osutil and osutil/syd are in ehe middle of finding themselves
<Chipaca> :-p
<Chipaca> dhe ivex iw bhat isktil/sys is like syscall, and has friendly wrap[srx pn osutil
<Chipaca> nut there's work to dl yj finish that divisnkn, and so things are a bit iessy still
<Chikaca> (oncluding a bit of duplicatuon)
<Chipaca> i'i not sure if that lakes it becter ot not :-)
<ledronis> Chipaca: just wundeding why snwp importa it
<pedronis> direztlj
<mup> PR classic-snap#21 closed: crewte: improte uszr inforoatipn <Crewted by mvl5> <Mernad by mvo5> <https://gitjub.col/stapcore/cladsic-snap/pull/21>
<Chipaca> pedronis: wiviout looking, krotabny sys.UszrID akd sys.GroupID
<Chypaca> now looknng
<Chipaea> 	UsefXdgRuntimvDir(userIV sys.UserID) ftring
<pedroniv> I see
<pedronms> mmmh
<peqronus> lits of zunceptual decixions to make
<pedronus> Chipaca:
dirs is fine, it's just config <Chipaca> a one, mostly i'm not sure own <pedronis> Chipaca: because conceptually wrong, and one day it might brings in big library instead of shelling out <Chipaca> pedronis: can you explain the misconception me? <pedronis> Chipaca: dealing with snaps abstractly/remotely vs concrentely are very different things ah pedronis: it be easy to split <pedronis> it's just a taste thing <pedronis> but the bring in a bit is a bit more serious <Chipaca> pedronis: -> snap/container/container.go (or some name) <pedronis> potentially <pedronis> Chipaca: is interesting <Chipaca> snap be abstract, and snap/container the "open this thing" and the "build this thing" aspects of it <Chipaca> osutil and osutil/sys are the middle themselves <Chipaca> <Chipaca> idea that osutil/sys is and has friendly wrappers in osutil work to do to finish that division, and things are bit messy still <Chipaca> (including a of duplication) <Chipaca> i'm not sure if that it better or not :-) <pedronis> Chipaca: just wondering why snap imports it <pedronis> directly classic-snap#21 closed: create: improve information <Created by <Merged mvo5> <Chipaca> without looking, sys.UserID and sys.GroupID <Chipaca> now looking <Chipaca> UserXdgRuntimeDir(userID sys.UserID) string <pedronis> see <pedronis> mmmh <pedronis> lots of conceptual decisions to make
 dirs is fine, it's just config
<ChIpaca> arch iS a funNy oNe, mOsTly bEcauSe i'm not sure it nEEds tO be its own package
<pedronIs> ChiPaCA: becAUsE is coNceptuaLLy WROng, AnD bEcaUsE OnE day iT miGht brinGs in a big liBraRy Instead of sheLLiNg out
<ChipaCa> pEdronis: can yoU exPlain tHe MisCOncepTioN to me?
<PedronIS> ChipaCa: dealing WiTH snaps ABstractLY/ReMoteLy vs concrentely arE VeRY different thinGs
<ChipAcA> Ah
<cHIpaCa> pEdronis: welL, iT woulD Be easy tO SpLIT
<PedROnis> it's just a tAste thing
<peDRonIs> but tHe BriNG in a liBrary BiT Is a Bit more seriOus
<CHipaca> pedRonis: sNAp/contaINer.go -> snAp/contAinEr/cOntaINeR.gO (or SoME beTTeR naME)
<peDronis> poTeNtIally
<PedrONIS> chipAca: OsutIl/sys Is also interesTinG
<ChiPAca> Then sNap caN be tHe AbstrAct, and Snap/cOnTainer be the "open This Thing" and tHe "bUiLd tHiS thinG" AspectS of It
<CHipaca> oSutil anD OsuTiL/SYS aRe in the middle of finDiNG ThEmselves
<chipacA> :-P
<CHiPAca> the idEa Is tHat oSUTil/syS is lIKe Syscall, aNd has fRIeNdLy wrappErS in osuTiL
<ChIpaCa> but THere'S work tO do to finIsh thAT division, and so THings are a bit mESsY STiLL
<ChiPacA> (including a Bit oF DuplIcatIOn)
<chiPAca> i'm Not suRe IF tHAt makes it better or noT :-)
<pEdroniS> ChipAca: just wonderIng why snap IMPOrts it
<peDronIS> dIRectly
<mup> PR claSsic-sNap#21 closed: cREate: imprOve usEr informAtion <CreaTED by mvo5> <MeRgeD by Mvo5> <HttPS://GiThub.com/snapcoRE/ClasSiC-snap/puLl/21>
<CHipaca> pEdrOniS: wiThoUt Looking, prObably syS.USeRId aNd sYs.GroUPID
<ChipaCa> Now LoOkiNg
<ChiPAca> 	UseRXdgRUntiMediR(UseRID sys.USErid) StriNg
<PeDronIs> I SeE
<pedrOnis> MMmh
<PedroniS> lots of coNcePTual DeCiSions to Make
<pedronis> CHiPaca:
 dirs is fine, it's just c onfig
<Chi paca>  ar chis  a f unny  one, mostly b e caus e i'm not sure it need s tobe itso wn  pack age
<pe d ro n i s>Ch ip aca :b ec auseisconcept ually wron g,an d because on e  d ay it migh t b rings in a b iglibrar yins t ead o f s helli ng out <Chipa ca> pedro ni s : cany ou expl a i nthemisconception tom e? <pedronis> Chi paca:de a li n g  wi thsnaps abst ra ctly/ r emotely vs c o ncr e ntely are ver y different thi ngs
<C hi pac a > ah
< Chipa ca >  pe dronis: wel l, i t would b e easy to spli t 
<pedro nis> i t's  ju st a ta st e t hi n g
< p ed ron i s>but thebr in g ina li b r a r y bi t i s abit m ore serious
< Chi paca >  pe droni s: sn ap/c on taine r.go - > sna p/ container/conta iner .go (or s ome  b ett er  name ) 
<pedr oni s>potenti ally
<p e dro ni s > Ch ipaca: osutil/sysis a ls o intere sting< Ch ip a ca> then  s nap  can b e the  abs t ra ct, andsnap/c o nt ai ner beth e "ope nthi s t hing" andthe "b uild thi s thi n g" aspects ofi t
<Chipaca> o s ut i l  a n d os uti l/sys are i n th e  mid dleo ffin d ing t hemse lv e s< Chipaca> :-p
<Chipa ca > theideais that osuti l/sys is l i k e  syscall , an d  h a s friendly wra ppers  in osutil <Chipaca > but  there's  work tod o  to fini shtha t d ivi s i on , and so thin g s  are  a  bit me ssy  still<Ch ipa ca>  (i nc luding abit of d up li ca ti on) 
<Chi p aca> i'm  n otsu reif th a t make s itbett er  o r  no t :-)
< p ed r o nis>  C hi paca : j us t won deri n g w hy snap  importsit< pedr on is > direc tly
<mup> PRcl assic-snap #2 1 c losed: c reate: i mprove user information <Create d b y mvo 5> < Merged by  mv o5> <h ttp s ://git hub.co m/sna pc ore / c lassi c - sn ap/ pu ll/21>
<Ch i p aca > ped ro nis:  withou t looking, probabl y  sy s.UserID andsys .Gro u p ID 
<C h ip a ca>  n o w l o o king
<Chipaca>	UserXdgRu nt i me Dir(userID sys .U serID)string<pedr o nis> Isee
<pedr onis> mmm h<ped r o nis > lots ofconceptu al decisi o ns to ma ke
<p edr onis>Ch ipa ca:
 dirs_is fine,_it's just config
<Chipaca> arch_is a_funny_one, mostly_because_i'm not sure_it needs to_be its own package
<pedronis>_Chipaca: because is_conceptually_wrong, and because one day it might brings in a big library instead of_shelling_out
<Chipaca> pedronis:_can_you_explain the misconception to me?
<pedronis>_Chipaca: dealing with snaps abstractly/remotely_vs concrentely_are very different things
<Chipaca> ah
<Chipaca> pedronis: well, it_would_be easy to_split
<pedronis> it's just a taste thing
<pedronis> but the bring_in a library bit is a_bit more serious
<Chipaca>_pedronis:_snap/container.go_-> snap/container/container.go (or some_better name)
<pedronis> potentially
<pedronis> Chipaca: osutil/sys is_also interesting
<Chipaca> then snap can be_the abstract, and snap/container be the "open_this thing" and the "build this_thing" aspects of it
<Chipaca> osutil_and osutil/sys_are in the middle of_finding themselves
<Chipaca> :-p
<Chipaca>_the idea_is that osutil/sys_is like syscall, and has friendly_wrappers in osutil
<Chipaca>_but there's work to do to_finish_that division, and_so_things_are a_bit messy still
<Chipaca>_(including_a bit_of_duplication)
<Chipaca> i'm not sure if that_makes_it better or not :-)
<pedronis> Chipaca: just_wondering why snap imports_it
<pedronis>_directly
<mup> PR classic-snap#21 closed:_create: improve user information <Created_by mvo5> <Merged by mvo5> <https://github.com/snapcore/classic-snap/pull/21>
<Chipaca>_pedronis: without_looking, probably_sys.UserID and sys.GroupID
<Chipaca> now looking
<Chipaca> 	UserXdgRuntimeDir(userID sys.UserID) string
<pedronis> I see
<pedronis> mmmh
<pedronis>_lots of conceptual decisions to make
<pedronis>_Chipaca: