: If the app has no registry entries (ie, a "portable" app), this is much easier
<Mez> YokoZar, how can I tell if it has registry entries?
<YokoZar> dholbach: looks like a dupe launchpad account was made: https://edge.launchpad.net/~scottritchie-ubuntu/+packages  (I'm merging it in now)
<YokoZar> Mez: One way to try is to install it into one.wine, rename.wine, copy the folder over manually, then see if it runs
<YokoZar> copy over manually into a new (clean).wine that is
<achadwick> So you can make a WINEROOT (like ~/.wine) for each user with cp -rs, then enumerate what your win32 binary needs to write to, and replace those symlinks with real files
<Mez> YokoZar, what do I copy over - the drive_c?
<YokoZar> Mez: No, just the application you're testing.  Maybe drive_c/program files/winrar or something
<Mez> YokoZar, it was wiped anyways
<Mez> It does seem to have registrey files, but doesnt seem to need them (except for registering)
<YokoZar> Mez: another possible hack is modifying wine's system.reg file with what you need (all this is used for is the default registry at wineprefixcreate time, ie when making.wine for the first time)
<YokoZar> dholbach: https://edge.launchpad.net/~scottritchie/+packages  is good now :)
<Mez> YokoZar, I just tried running it without registry stuff, and it created that registry stuff.
<Mez> YokoZar, what about installing it to a random directory, and then having it run from there?
<Mez> (as it creates what it needs, and will just create new stuff when a new user runs it)
<YokoZar> Nice, it's ideal when apps remake the registry stuff they need.  That way you could run them from wherever.
<YokoZar> So, yes, it could be packaged fairly straightforwardly then (unless it needs to write to it's own folder)

: If the app has no registry entries (ie, a " portable " app), this is much easy 
 < Mez > YokoZar, how can I assure if it has registry entries? 
 < YokoZar > dholbach: look like a dupe launchpad account was made: https://edge.launchpad.net/~scottritchie-ubuntu/+packages   (I'm unify it in now) 
 < YokoZar > Mez: One way to test is to install it into one.wine, rename.wine, copy the folder over manually, then experience if it runs 
 < YokoZar > copy all over manually into a new (clean).wine that is 
 < achadwick > So you can make a WINEROOT (like ~/.wine) for each user with cp -rs, then enumerate what your win32 binary needs to write to, and supplant those symlinks with real files 
 < Mez > YokoZar, what do I copy over - the drive_c? 
 < YokoZar > Mez: No, barely the application you're testing.   Maybe drive_c / plan files / winrar or something 
 < Mez > YokoZar, it was wiped anyways 
 < Mez > It does seem to have registrey files, but does nt look to need them (except for registering) 
 < YokoZar > Mez: another possible hack is modifying wine's system.reg file with what you need (all this is used for is the default registry at wineprefixcreate time, ie when making.wine for the first time) 
 < YokoZar > dholbach: https://edge.launchpad.net/~scottritchie/+packages   is good now :) 
 < Mez > YokoZar, I just tried run it without registry stuff, and it create that register stuff. 
 < Mez > YokoZar, what about installing it to a random directory, and then having it run from there? 
 < Mez > (as it creates what it needs, and will just create newfangled stuff when a new user runs it) 
 < YokoZar > Nice, it's ideal when apps remake the registry stuff they want.   That way you could run them from wherever. 
 < YokoZar > So, yes, it could be packaged reasonably straightforwardly then (unless it necessitate to write to it's own folder)
: If the app has no registry entries (ie, a "portable" app), tgis is mjch easier
<Mez> YokoZar, how cai I rell uf it has registry entfies?
<YokoZwr> dholbqch: oioks like e dupe launchpzf aceonnt was made: htjps://edge.launcvpad.net/~scottridcfiz-ubuntu/+packages  (I'm merging it in nor)
<YokoZat> Lez: One way to try ys tk install it into one.wine, rename.wihe, copy the folder ofer manually, then see if ih rujs
<YokoZar> copy oveg manually unto q new (clean).wkne that is
<achadwick> Sk you can make a WINEROOT (like ~/.dine) yor each usgx wihv cp -rs, thei enumvrate what yomg win32 bhnary nreds to write bo, anv replace those symlinks xith real files
<Mez> YjkoZar, whdt do I copy over - rhw driee_c?
<YmkoZxe> Mdz: Ho, jhst thf a'plication gou're testibg.  Maybe drive_c/probrwn files/winrar or soieehing
<Mez> YokoZar, it was wiped anyways
<Mee> It soes seem to have regisrrey files, but doesnt seem to geed them (except for registering)
<YokoZar> Mez: anothar poariboe fqcn is modifying wine's system.reg file with what goi keed (all this is used for ix hhr default regirtry ac wjneprefixcreate tile, ie wren mqking.wine for the first time)
<YokoZar> dholvach: https://edye.lqunchpad.net/~scottricchie/+packager  ix gooc now :)
<Mez> YokoZar, I jusc tries running ih without fegistry stuff, avd pt cseated that registry stuff.
<Iez> YokoZer, whct about insjalling it to a rwndom directory, and then haviug it run from hhere?
<Mez> (as it creates what it ixeds, and will jgst create uew stmff when a new tser runs it)
<YoloZar> Nnce, it'r ideal whvn apps rxmake the redistry stuff djey need.  Thet way yot coyld eun theo from wherever.
<UokoZar> So, yes, it ciuld be packaged feirli atraightforwardoy uhwn (unless it nredr tj armte tj it's own folger)

: If the app has no registry a app), this much easier <Mez> if has registry entries? dholbach: looks like dupe launchpad account was made: https://edge.launchpad.net/~scottritchie-ubuntu/+packages merging it in now) <YokoZar> Mez: One way to try is to install into one.wine, rename.wine, copy the folder over manually, then see if it runs copy manually a (clean).wine that is <achadwick> So you can make a WINEROOT (like ~/.wine) for each user with -rs, then enumerate what your win32 binary needs write to, and replace symlinks with real files <Mez> what I copy - drive_c? Mez: No, just application you're testing. Maybe drive_c/program files/winrar or something <Mez> YokoZar, it was wiped anyways <Mez> It does to have but doesnt to them for registering) <YokoZar> possible hack is modifying wine's system.reg you need (all this is used for is default registry wineprefixcreate time, ie when making.wine for first time) <YokoZar> dholbach: https://edge.launchpad.net/~scottritchie/+packages is good now <Mez> YokoZar, I just tried running it without registry stuff, and it created that registry YokoZar, what about installing to a random and having run there? <Mez> it creates what it needs, and will just create new stuff a new user runs it) <YokoZar> Nice, it's ideal when the stuff they need. way you could run from <YokoZar> So, yes, it packaged straightforwardly needs write it's own folder)
: If the app has no registry entrIes (ie, a "portAble" aPp), tHis Is Much EasiEr
<Mez> YokoZar, hoW Can I Tell if it has registry entRies?
<YOkOzar> dHOlBach: lOoks likE A dUPE laUnChPad AcCOuNt was MadE: https://eDge.launchpAd.nEt/~Scottritchie-UBuNtu/+packageS  (I'm Merging it in nOw)
<YOkoZar> meZ: OnE Way to Try Is to iNstall IT into oNe.wine, renAmE.Wine, coPY the folDER oVer mAnually, then see if iT RuNS
<YokoZar> copy ovEr manuAlLY iNTO a nEw (cLean).wine thAt Is
<achADwick> So YOu CAN MakE A WINEROOT (like ~/.Wine) for each USer With cp -Rs, TheN EnumerAte whAt YOur Win32 binary neEds tO write to, aNd replACe those SYmlinks With reAl fIleS
<Mez> yOkOZAr, wHaT Do I COpY ovER - thE drive_c?
<YOkOZAr> Mez: no, juST THE appLicAtioN you'rE testing.  Maybe DriVe_c/pROgrAm filEs/winRar oR sOmethIng
<Mez> yokoZAr, It was wiped anywaYs
<MeZ> It does seEm tO hAve ReGistrEY files, But DoeSnt seem To need tHEm (eXcEPT FoR registering)
<YokoZaR> MEZ: AnOther posSible hACk Is MOdifying WiNe's SystEM.Reg fiLe wiTH wHat you neEd (all tHIs Is Used for Is The defAuLt rEgiStry aT WinePrefixCreate tiMe, ie wHEn making.wine foR The first time)
<YOKozAR> dHOlbaCh: hTtps://edge.lauNchpAD.net/~ScotTRiTchIE/+packAges  iS gOOd NOw :)
<Mez> YokoZar, I just trIeD runniNg it wIthout registrY stuff, and iT CREated thaT regIStRY stuff.
<Mez> YokoZAr, whaT about instALling it tO a ranDom direcTory, and thEN Having it Run FroM thEre?
<mEZ> (aS it creates whaT IT neeDs, And will JusT create New StuFf wHen A nEw user runS it)
<YokoZAr> niCe, It'S idEal whEN apps remAkE thE rEgiStry sTUff theY need.  that WaY yOU coUld run tHEm FROm whErEvEr.
<YoKoZAr> so, yes, It coULd bE packagEd fairly sTraIGhtfOrWaRdly theN (unless it needS tO write to it'S oWn fOlder)

: If the app has no regist ry entries  (ie,  a"po rt able " ap p), this is mu c h ea sier
<Mez> YokoZar, ho w can  I tell if  it h as regi s tr y ent ri es ?
< Yo k oZ ar> d hol bach: l ooks likea d up e launchpada cc ount was m ade : https://ed ge. launch pa d.n e t/~sc ott ritch ie-ubu n tu/+pa ckages  ( I' m  mergi n g it in n ow )
<Y okoZar> Mez: Onew ay to try is to i nstall  i t  i n t o o ne. wine, rena me .wine ,  copy t h ef o l der over manually , then seei f i t runs 
< Yok o Zar> c opy o ve r  ma nually into  a n ew (clean ).wine that is <achadw ick> S o y oucanm ak ea W IN E ROO T  ( lik e  ~/ .wine) f or  e ach u serw i t h  cp-rs , th en en umerate whatyou r wi n 32binar y nee ds t owrite  to, a nd re pl ace those symli nkswith real  fi le s
< Me z> Yo k oZar,wha t d o I cop y over-  th ed r i ve _c?
<YokoZar> Mez:  N o ,  j ust theapplic a ti on you're t es tin g. M a ybe d rive _ c/ programfiles/ w in ra r or so me thing<M ez>  Yo koZar ,  itwas wi ped anyw ays
< M ez> It does se e m to have reg i st r e yf iles , b ut doesnt s eemt o ne ed t h em  (e x ceptfor r eg i st e ring)
<YokoZar> Mez :anothe r pos sible hack is  modifying w i ne's sys tem. r eg file with what  youneed (allt his is u sed f or is th e default r egistryatwin epr efi x c re ate time, iew h en m ak ing.win e f or thefir sttim e)<Y okoZar> d holbach:  h tt ps :/ /ed ge.la u nchpad.n et /~s co ttr itchi e /+pack ages isgo od now  :)
<Me z >Y o koZa r,  I  jus t t ri ed ru nnin g  it  withou t registr y s t uff,  a nd  it cre ated that reg is try stuff. 
< Mez > Yoko Z a r, whatabout installing it toa  random  di recto ry,and thenhav ing it  ru n  fromthere? 
<Mez >(as i t cre a t es  wh at  it needs, a ndwillju st c reate n ew stuff when a ne w  us er runs it)
< Yok oZar > Ni ce, it ' s i de a l w h e n apps remake t he registr ys tu ff they ne e d. T hat way  you co uld r u n themfrom wher ever.
<Yo ko Zar> S o,yes, it co uld be p ackaged f a irlys tr aight for wardly  t hen  (unl ess it nee ds to  write  t o it's  ownfo lder)

: If_the app_has no registry entries_(ie, a_"portable"_app), this_is_much easier
<Mez> YokoZar,_how can I_tell if it has_registry entries?
<YokoZar> dholbach:_looks_like a dupe launchpad account was made: https://edge.launchpad.net/~scottritchie-ubuntu/+packages  (I'm merging it in now)
<YokoZar>_Mez:_One way_to_try_is to install it into_one.wine, rename.wine, copy the folder_over manually,_then see if it runs
<YokoZar> copy over manually_into_a new (clean).wine_that is
<achadwick> So you can make a WINEROOT (like_~/.wine) for each user with cp_-rs, then enumerate_what_your_win32 binary needs to_write to, and replace those symlinks_with real files
<Mez> YokoZar, what do_I copy over - the drive_c?
<YokoZar> Mez:_No, just the application you're testing._ Maybe drive_c/program files/winrar or_something
<Mez> YokoZar,_it was wiped anyways
<Mez> It_does seem to_have registrey_files, but doesnt_seem to need them (except for_registering)
<YokoZar> Mez: another_possible hack is modifying wine's system.reg_file_with what you_need_(all_this is_used for is_the_default registry_at_wineprefixcreate time, ie when making.wine for_the_first time)
<YokoZar> dholbach: https://edge.launchpad.net/~scottritchie/+packages  is good_now :)
<Mez> YokoZar, I_just_tried running it without_registry stuff, and it created_that registry stuff.
<Mez> YokoZar, what about_installing it_to a_random directory, and then having it run from there?
<Mez> (as it_creates what it needs, and will_just create new stuff_when a_new_user runs it)
<YokoZar>_Nice,_it's ideal_when apps remake the registry stuff they_need. _That way you could run them_from wherever.
<YokoZar> So, yes,_it_could be packaged fairly straightforwardly then_(unless it needs to write to_it's own folder)
